Vulnerabilities exploitable today
354,538in 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,634
- High9,425
- Medium7,595
- Low697
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2025-47590—5.0%
——1——CVE-2026-21317—5.0%
——1——CVE-2020-0243—5.0%
——1——CVE-2024-34022—5.0%
——1——CVE-2024-47256—5.0%
——1——CVE-2025-47459—5.0%
——1——CVE-2026-498027.0 HIG5.0%
——1Concurrent execution using shared resource with improper synchronization ('race condition') in Windows USB Print Driver allows an authorized attacker to elevate privileges locally.9dCVE-2026-26172—5.0%
——1——CVE-2026-21332—5.0%
——1——CVE-2023-53192—5.0%
——1——CVE-2024-54127—5.0%
——1——CVE-2025-47596—5.0%
——1——CVE-2026-21339—5.0%
——1——CVE-2026-21314—5.0%
——1——CVE-2020-3442—5.0%
——1——CVE-2022-485753.5 LOW5.0%
——1A person with access to a Mac may be able to bypass Login Window. A consistency issue was addressed with improved state handling. This issue is fixed in macOS Monterey 12.4.8dCVE-2025-47606—5.0%
——1——CVE-2023-43753—5.0%
——1——CVE-2026-21313—5.0%
——1——CVE-2026-27150—5.0%
——1——CVE-2022-50488—5.0%
——1——CVE-2025-47542—5.0%
——1——CVE-2026-21319—5.0%
——1——CVE-2025-47523—5.0%
——1——CVE-2026-504047.0 HIG5.0%
——1Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Media allows an authorized attacker to elevate privileges locally.9dCVE-2021-30260—5.0%
——1——CVE-2026-504507.8 HIG5.0%
——1Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Wireless Wide Area Network Service allows an authorized attacker to elevate privileges locally.9dCVE-2026-568473.3 LOW5.0%
——1A flaw in Node.js Permission Model enforcement allows `trace_events.createTracing().enable()` Writes Trace Logs Outside `--allow-fs-write`.
This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations.
This vulnerability affects Node.js **22.x**, **24.x**, and **26.x**.1dCVE-2025-71133—5.0%
——1——CVE-2026-21315—5.0%
——1——CVE-2026-498067.0 HIG5.0%
——1Concurrent execution using shared resource with improper synchronization ('race condition') in Windows USB Print Driver allows an authorized attacker to elevate privileges locally.9dCVE-2025-47519—5.0%
——1——CVE-2025-47609—5.0%
——1——CVE-2026-497847.0 HIG5.0%
——1Concurrent execution using shared resource with improper synchronization ('race condition') in Microsoft Windows App Store allows an authorized attacker to elevate privileges locally.8dCVE-2026-498087.8 HIG5.0%
——1Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Kernel allows an authorized attacker to elevate privileges locally.9dCVE-2026-541117.0 HIG5.0%
——1Concurrent execution using shared resource with improper synchronization ('race condition') in Windows USB Print Driver allows an authorized attacker to elevate privileges locally.9dCVE-2025-20118—5.0%
——1——CVE-2025-383727.8 HIG5.0%
——1In the Linux kernel, the following vulnerability has been resolved:
RDMA/mlx5: Fix unsafe xarray access in implicit ODP handling
__xa_store() and __xa_erase() were used without holding the proper lock,
which led to a lockdep warning due to unsafe RCU usage. This patch
replaces them with xa_store() and xa_erase(), which perform the necessary
locking internally.
=============================
WARNING: suspicious RCPU usage
6.14.0-rc7_for_upstream_debug_2025_03_18_15_01 #1 Not tainted
-----------------------------
./include/linux/xarray.h:1211 suspicious rcu_dereference_protected() usage!
other info that might help us debug this:
rcu_scheduler_active = 2, debug_locks = 1
3 locks held by kworker/u136:0/219:
at: process_one_work+0xbe4/0x15f0
process_one_work+0x75c/0x15f0
pagefault_mr+0x9a5/0x1390 [mlx5_ib]
stack backtrace:
CPU: 14 UID: 0 PID: 219 Comm: kworker/u136:0 Not tainted
6.14.0-rc7_for_upstream_debug_2025_03_18_15_01 #1
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS
rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014
Workqueue: mlx5_ib_page_fault mlx5_ib_eqe_pf_action [mlx5_ib]
Call Trace:
dump_stack_lvl+0xa8/0xc0
lockdep_rcu_suspicious+0x1e6/0x260
xas_create+0xb8a/0xee0
xas_store+0x73/0x14c0
__xa_store+0x13c/0x220
? xa_store_range+0x390/0x390
? spin_bug+0x1d0/0x1d0
pagefault_mr+0xcb5/0x1390 [mlx5_ib]
? _raw_spin_unlock+0x1f/0x30
mlx5_ib_eqe_pf_action+0x3be/0x2620 [mlx5_ib]
? lockdep_hardirqs_on_prepare+0x400/0x400
? mlx5_ib_invalidate_range+0xcb0/0xcb0 [mlx5_ib]
process_one_work+0x7db/0x15f0
? pwq_dec_nr_in_flight+0xda0/0xda0
? assign_work+0x168/0x240
worker_thread+0x57d/0xcd0
? rescuer_thread+0xc40/0xc40
kthread+0x3b3/0x800
? kthread_is_per_cpu+0xb0/0xb0
? lock_downgrade+0x680/0x680
? do_raw_spin_lock+0x12d/0x270
? spin_bug+0x1d0/0x1d0
? finish_task_switch.isra.0+0x284/0x9e0
? lockdep_hardirqs_on_prepare+0x284/0x400
? kthread_is_per_cpu+0xb0/0xb0
ret_from_fork+0x2d/0x70
? kthread_is_per_cpu+0xb0/0xb0
ret_from_fork_asm+0x11/0x201dCVE-2021-47829—5.0%
——1——CVE-2025-20158—5.0%
——1——