Vulnerabilities exploitable today
379,234in 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,721
New KEV · 24H0
Exploit Today ≥ 701,654
Distribution · last window
- Critical2,390
- High8,612
- Medium7,064
- Low795
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2015-7962—34.8%
——10——CVE-2024-6086—34.8%
——10——CVE-2018-5731—34.8%
——10——CVE-2024-51032—34.8%
——10——CVE-2023-4916—34.8%
——10——CVE-2024-11895—34.8%
——10——CVE-2025-63209—34.8%
——10——CVE-2025-0752—34.8%
——10——CVE-2025-412739.8 CRI34.7%
——10Nozomi Networks Labs identified a CWE-288: Authentication Bypass Using an Alternate Path or Channel in the Console WebUI in Waterfall WF-500 TX and RX Hosts in version 7.9.1.0 R2502171040 that allows remote unauthenticated attackers to bypass authentication of the Console web application and perform actions as an authenticated user.65dCVE-2024-5235—34.7%
——10——CVE-2024-4909—34.7%
——10——CVE-2024-5238—34.7%
——10——CVE-2019-25223—34.7%
——10——CVE-2024-5109—34.7%
——10——CVE-2026-609418.7 HIG34.7%
——10Vulnerability in the Oracle Service Fulfillment Manager product of Oracle E-Business Suite (component: Fulfillment Engine). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle Service Fulfillment Manager. While the vulnerability is in Oracle Service Fulfillment Manager, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Service Fulfillment Manager accessible data as well as unauthorized access to critical data or complete access to all Oracle Service Fulfillment Manager accessible data. CVSS 3.1 Base Score 8.7 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N).42dCVE-2019-1726—34.7%
——10——CVE-2024-5108—34.7%
——10——CVE-2023-47096—34.7%
——10——CVE-2025-24018—34.7%
——10——CVE-2026-1425—34.7%
——10——CVE-2026-896549.8 CRI34.7%
——10In the Linux kernel, the following vulnerability has been resolved:
ceph: fix UAF in check_new_map() on session freed during unlock
check_new_map() iterates mdsc->sessions[] and for each active session
drops mdsc->mutex to perform per-session operations. The forced-close
path (rank removed from map) correctly takes a reference on s via
ceph_get_mds_session() before releasing mdsc->mutex, but three other
paths do not:
Path A (address changed): mutex_unlock → mutex_lock(&s->s_mutex)
Path B (reconnect): mutex_unlock → send_mds_reconnect(mdsc, s)
Path C (active transition): mutex_unlock → mutex_lock(&s->s_mutex)
Without the extra reference, another thread can acquire mdsc->mutex
during the unlock window, call __unregister_session() which drops the
last reference on s, and free it. The original thread then accesses
freed memory via s->s_mutex.
Fix by adding ceph_get_mds_session(s) before each mutex_unlock and
ceph_put_mds_session(s) after the corresponding mutex_lock, matching
the pattern already used in the forced-close path.
Race timeline (Path A):
Thread A (check_new_map) Thread B (another map update
holds mdsc->mutex or session teardown)
-------------------------- --------------------------
s = mdsc->sessions[i]
(refcount == 1, held only by
sessions[] array)
mutex_unlock(&mdsc->mutex)
---> acquires mdsc->mutex
__unregister_session(mdsc, s)
sessions[i] = NULL
ceph_put_mds_session(s)
refcount: 1 -> 0
kfree(s) <--- freed!
mutex_lock(&s->s_mutex)
UAF on freed s->s_mutex11dCVE-2023-45203—34.7%
——10——CVE-2024-7425—34.7%
——10——CVE-2024-53319—34.7%
——10——CVE-2026-203109.1 CRI34.7%
——10As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco Catalyst SD-WAN engineering team has conducted a comprehensive internal security review. This review resulted in software hardening releases that address multiple internally discovered vulnerabilities.
The vulnerabilities tracked by CVE-2026-20310 are related to improper link resolution before file access issues that are grouped under the Common Weakness Enumeration (CWE) CWE-59.40dCVE-2025-59151—34.7%
——10——CVE-2024-11553—34.7%
——10——CVE-2024-5110—34.7%
——10——CVE-2024-51495—34.7%
——10——CVE-2019-16752—34.7%
——10——CVE-2023-1071—34.7%
——10——CVE-2025-54299—34.7%
——10——CVE-2023-37830—34.7%
——10——CVE-2024-4908—34.7%
——10——CVE-2026-896779.8 CRI34.7%
——10In the Linux kernel, the following vulnerability has been resolved:
nfsd: fix possible fh_compose of wrong dentry in nfsd4_create_file()
dentry_create() can hypothetically provide a different dentry than the
one passed in. This could happen, for example, if the exported
filesystem is NFS, and the server returned to OPEN a filehandle which
matched a directory that was already in the dcache. Clearly this would
not be expected!
If this were to happen the dentry (child) that was already stored in
resfhp could be freed and later dereferenced.
We shouldn't call fh_compose() until we are certain that we have the
final dentry, so this patch moved the fh_compose() call to two places:
one for the case where the target already exists, and one after
dentry_create() where it was created.11dCVE-2000-1059—34.7%
——10——CVE-2024-51494—34.7%
——10——CVE-2021-20738—34.7%
——10——CVE-2024-5233—34.7%
——10——CVE-2024-52895—34.7%
——10——