Vulnerabilities exploitable today
354,630in current view
Single score combining CVSS, KEV membership and EPSS. Every CVE with its own record — timeline from publication to active exploitation.
In KEV catalog1,656
New KEV · 24H0
Exploit Today ≥ 701,601
Distribution · last window
- Critical2,600
- High9,389
- Medium7,532
- Low703
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-0972—5.1%
——2——CVE-2026-483535.5 MED5.1%
——2CAI Content Credentials is affected by an Improper Input Validation vulnerability that could lead to arbitrary file system read. An attacker could exploit this vulnerability to access sensitive files and directories outside the intended access scope. Exploitation of this issue requires user interaction in that a victim must open a malicious file.15dCVE-2025-64204—5.1%
——2——CVE-2026-32451—5.1%
——2——CVE-2026-27017—5.1%
——2——CVE-2023-24016—5.1%
——2——CVE-2025-3426—5.1%
——2——CVE-2021-29570—5.1%
——2——CVE-2019-9269—5.1%
——2——CVE-2025-64361—5.1%
——2——CVE-2025-64362—5.1%
——2——CVE-2026-616435.9 MED5.1%
——2FastGPT is a knowledge-based AI application platform. From 4.14.17 until 4.15.0-beta5, an authenticated FastGPT user can save a workflow node that points to another user's private HTTP toolset by using a crafted saved tool id such as http-<victim_toolset_app_id>/<tool_name>. The normal toolset routes deny access, but the workflow save and runtime path did not apply the same authorization check to the referenced toolset, allowing /api/v2/chat/completions to resolve the saved reference and execute the victim-owned HTTP tool. This issue is fixed in version 4.15.0-beta5.11dCVE-2025-58864—5.1%
——2——CVE-2025-58985—5.1%
——2——CVE-2025-38222—5.1%
——2——CVE-2025-58863—5.1%
——2——CVE-2025-62974—5.1%
——2——CVE-2025-58632—5.1%
——2——CVE-2025-30652—5.1%
——2——CVE-2025-58882—5.1%
——2——CVE-2026-5185—5.1%
——2——CVE-2020-36933—5.1%
——2——CVE-2026-21674—5.1%
——2——CVE-2026-48936—5.1%
——2——CVE-2021-37646—5.1%
——2——CVE-2026-41426—5.1%
——2——CVE-2026-20653—5.1%
——2——CVE-2025-384637.8 HIG5.1%
——2In the Linux kernel, the following vulnerability has been resolved:
tcp: Correct signedness in skb remaining space calculation
Syzkaller reported a bug [1] where sk->sk_forward_alloc can overflow.
When we send data, if an skb exists at the tail of the write queue, the
kernel will attempt to append the new data to that skb. However, the code
that checks for available space in the skb is flawed:
'''
copy = size_goal - skb->len
'''
The types of the variables involved are:
'''
copy: ssize_t (s64 on 64-bit systems)
size_goal: int
skb->len: unsigned int
'''
Due to C's type promotion rules, the signed size_goal is converted to an
unsigned int to match skb->len before the subtraction. The result is an
unsigned int.
When this unsigned int result is then assigned to the s64 copy variable,
it is zero-extended, preserving its non-negative value. Consequently, copy
is always >= 0.
Assume we are sending 2GB of data and size_goal has been adjusted to a
value smaller than skb->len. The subtraction will result in copy holding a
very large positive integer. In the subsequent logic, this large value is
used to update sk->sk_forward_alloc, which can easily cause it to overflow.
The syzkaller reproducer uses TCP_REPAIR to reliably create this
condition. However, this can also occur in real-world scenarios. The
tcp_bound_to_half_wnd() function can also reduce size_goal to a small
value. This would cause the subsequent tcp_wmem_schedule() to set
sk->sk_forward_alloc to a value close to INT_MAX. Further memory
allocation requests would then cause sk_forward_alloc to wrap around and
become negative.
[1]: https://syzkaller.appspot.com/bug?extid=de6565462ab540f50e472dCVE-2021-37668—5.1%
——2——CVE-2025-68525—5.1%
——2——CVE-2025-48105—5.1%
——2——CVE-2026-108554.3 MED5.1%
——2An authorization flaw existed in the MISP Event Template Importer overwrite workflow. When importing an event template in overwrite mode, the application checked whether a matching template already existed but did not verify that the importing user belonged to the organization that owned the existing template. As a result, an authenticated user with access to the template import functionality could forcibly overwrite an event template owned by another organization.
Successful exploitation could allow unauthorized modification of another organization’s event template, potentially altering template structure, attributes, or metadata used for subsequent event creation or sharing workflows. Site administrators are not affected by this restriction, as they are explicitly allowed to overwrite templates across organizations.
The issue was fixed by enforcing an ownership check before overwrite: non-site-admin users may only overwrite templates owned by their own organization.9dCVE-2026-119814.3 MED5.1%
——2The GiveWP plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.15.3 This is due to missing nonce validation on the give_set_notification_status_handler() function. This makes it possible for unauthenticated attackers to disable donation email notifications via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.30dCVE-2025-62987—5.1%
——2——CVE-2025-62969—5.1%
——2——CVE-2025-62968—5.1%
——2——CVE-2025-58997—5.1%
——2——CVE-2025-63010—5.1%
——2——CVE-2022-39861—5.1%
——2——CVE-2021-0924—5.1%
——2——