Vulnerabilities exploitable today
373,010in 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,709
New KEV · 24H0
Exploit Today ≥ 701,644
Distribution · last window
- Critical2,219
- High8,127
- Medium6,187
- Low611
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2017-2330—24.4%
——7——CVE-2024-6713—24.4%
——7——CVE-2008-5299—24.4%
——7——CVE-2023-1493—24.4%
——7——CVE-2024-10250—24.4%
——7——CVE-2024-22150—24.4%
——7——CVE-2025-20670—24.4%
——7——CVE-2024-2017—24.4%
——7——CVE-2021-3947—24.4%
——7——CVE-2024-40841—24.4%
——7——CVE-2024-40675—24.4%
——7——CVE-2022-2961—24.4%
——7——CVE-2026-581598.2 HIG24.4%
——7Apache Traffic Server can bypass IP access controls on UDS listeners and through ACL matching errors.
This issue affects Apache Traffic Server: from 8.0.0 through 8.1.9, from 9.0.0 through 9.2.14, from 10.0.0 through 10.1.3.
Users are recommended to upgrade to version 9.2.15 or 10.1.4, which fix the issue.40dCVE-2023-50875—24.4%
——7——CVE-2001-0141—24.4%
——7——CVE-2000-0029—24.4%
——7——CVE-2024-8726—24.4%
——7——CVE-2024-22158—24.4%
——7——CVE-2016-5849—24.4%
——7——CVE-2014-8527—24.4%
——7——CVE-2022-40184—24.4%
——7——CVE-2024-12211—24.4%
——7——CVE-2001-1276—24.4%
——7——CVE-2023-1644—24.4%
——7——CVE-2026-607918.1 HIG24.4%
——7Vulnerability in the Siebel CRM Deployment product of Oracle Siebel CRM (component: Application Interface). Supported versions that are affected are 17.0-26.6. Easily exploitable vulnerability allows unauthenticated attacker with access to the physical communication segment attached to the hardware where the Siebel CRM Deployment executes to compromise Siebel CRM Deployment. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Siebel CRM Deployment accessible data as well as unauthorized access to critical data or complete access to all Siebel CRM Deployment accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).23dCVE-2024-34928—24.4%
——7——CVE-2024-11490—24.4%
——7——CVE-2026-724698.8 HIG24.4%
——7In the Linux kernel, the following vulnerability has been resolved:
xprtrdma: Fix ep kref imbalance on ADDR_CHANGE
rpcrdma_cm_event_handler() falls through to the disconnected: label
on RDMA_CM_EVENT_ADDR_CHANGE and calls rpcrdma_ep_put() with no
matching get when the event arrives before RDMA_CM_EVENT_ESTABLISHED.
The kref then underflows during connect teardown and
rpcrdma_xprt_disconnect() operates on a freed ep.
Reference counts across a normal connection lifecycle:
rpcrdma_ep_create() kref_init ->1
rpcrdma_xprt_connect() ep_get ->2 (before post_recvs)
RDMA_CM_EVENT_ESTABLISHED ep_get ->3
RDMA_CM_EVENT_DISCONNECTED ep_put ->2
rpcrdma_xprt_drain() ep_put ->1
rpcrdma_xprt_disconnect() tail ep_put ->0 (ep_destroy)
The connect-time get in rpcrdma_xprt_connect(), taken just before
rpcrdma_post_recvs() "while there are outstanding Receives," is
balanced by rpcrdma_xprt_drain. ADDR_CHANGE before ESTABLISHED has
no get to consume, so its put drops the count to 1 and the drain
put then frees the ep while rpcrdma_xprt_disconnect() still holds a
pointer to it.
Fix by dispatching on the prior re_connect_status via xchg(): for
prev == 0 (pre-ESTABLISHED) wake the connect waiter and return with
no put; for prev == 1 call rpcrdma_force_disconnect() and return.
The case-1 arm relies on the subsequent RDMA_CM_EVENT_DISCONNECTED
event -- reliably delivered when rdma_disconnect() is called on a
still-connected cm_id -- to balance the ESTABLISHED get;
rpcrdma_xprt_drain() continues to balance only that connect-time
get. Any other prior value means teardown is already in flight.27dCVE-2022-3459—24.4%
——7——CVE-2024-6665—24.4%
——7——CVE-2026-706574.3 MED24.4%
——7Copyparty is a portable file server. Prior to 1.20.17, copyparty volumes with the dk or dks directory-key flag combined with the fk or fka file-key flag can convert a valid file key into a directory key, granting read access to the containing folder. This vulnerability was only reachable if both types of keys (filekeys and dirkeys) were manually enabled in the volume flags simultaneously. This issue is fixed in version 1.20.17.24dCVE-2024-12096—24.4%
——7——CVE-2024-22310—24.4%
——7——CVE-2011-3585—24.4%
——7——CVE-2024-25593—24.4%
——7——CVE-2015-3339—24.4%
——7——CVE-2026-490918.0 HIG24.4%
——7Improper Output Neutralization for Logs (CWE-117) in Kibana can lead to log injection via Log Injection-Tampering-Forging (CAPEC-93). An attacker can supply specially crafted input that is written to log files without proper neutralization. When the log files are subsequently viewed in a terminal that interprets control sequences, the injected content may alter the displayed log data.72dCVE-2024-29107—24.4%
——7——CVE-2025-48219—24.4%
——7——CVE-2023-1492—24.4%
——7——