Vulnerabilities exploitable today
351,724in 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,651
New KEV · 24H0
Exploit Today ≥ 701,587
Distribution · last window
- Critical1,765
- High5,628
- Medium4,518
- Low412
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-7913—1.6%
——0——CVE-2026-28889—1.6%
——0——CVE-2021-25503—1.6%
——0——CVE-2022-20430—1.6%
——0——CVE-2025-9408—1.6%
——0——CVE-2023-24853—1.6%
——0——CVE-2025-9127—1.6%
——0——CVE-2026-31252—1.6%
——0——CVE-2023-33021—1.6%
——0——CVE-2026-12781—1.6%
——0——CVE-2026-7990—1.6%
——0——CVE-2022-20348—1.6%
——0——CVE-2023-43535—1.6%
——0——CVE-2023-33039—1.6%
——0——CVE-2025-0045—1.6%
——0——CVE-2025-32060—1.6%
——0——CVE-2024-43087—1.6%
——0——CVE-2026-21768—1.6%
——0——CVE-2025-14465—1.6%
——0——CVE-2026-532507.8 HIG1.6%
——0In the Linux kernel, the following vulnerability has been resolved:
xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata()
The TX metadata area resides in the UMEM buffer which is memory-mapped
and concurrently writable by userspace. In xsk_skb_metadata(),
csum_start and csum_offset are read from shared memory for bounds
validation, then read again for skb assignment. A malicious userspace
application can race to overwrite these values between the two reads,
bypassing the bounds check and causing out-of-bounds memory access
during checksum computation in the transmit path.
Fix this by reading csum_start and csum_offset into local variables
once, then using the local copies for both validation and assignment.
Note that other metadata fields (flags, launch_time) and the cached
csum fields may be mutually inconsistent due to concurrent userspace
writes, but this is benign: the only security-critical invariant is
that each field's validated value is the same one used, which local
caching guarantees.14dCVE-2025-0031—1.6%
——0——CVE-2026-24923—1.6%
——0——CVE-2026-6424—1.6%
——0Use-after-free vulnerability in ESET Linux products potentially allowed an attacker to trigger kernel panic on the system6dCVE-2026-5164—1.6%
——0——CVE-2021-0619—1.6%
——0——CVE-2022-20076—1.6%
——0——CVE-2026-41398—1.6%
——0——CVE-2022-20198—1.6%
——0——CVE-2024-8298—1.6%
——0——CVE-2023-33905—1.6%
——0——CVE-2023-22675—1.6%
——0——CVE-2025-67465—1.6%
——0——CVE-2023-33904—1.6%
——0——CVE-2023-33903—1.6%
——0——CVE-2025-64239—1.6%
——0——CVE-2025-38462—1.6%
——0——CVE-2025-20233—1.6%
——0——CVE-2026-39454—1.6%
——0——CVE-2021-25511—1.6%
——0——CVE-2025-47274—1.6%
——0——