Vulnerabilities exploitable today
365,446in 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,682
New KEV · 24H0
Exploit Today ≥ 701,626
Distribution · last window
- Critical2,341
- High10,014
- Medium4,921
- Low461
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2025-383778.8 HIG14.3%
——4In the Linux kernel, the following vulnerability has been resolved:
rose: fix dangling neighbour pointers in rose_rt_device_down()
There are two bugs in rose_rt_device_down() that can cause
use-after-free:
1. The loop bound `t->count` is modified within the loop, which can
cause the loop to terminate early and miss some entries.
2. When removing an entry from the neighbour array, the subsequent entries
are moved up to fill the gap, but the loop index `i` is still
incremented, causing the next entry to be skipped.
For example, if a node has three neighbours (A, A, B) with count=3 and A
is being removed, the second A is not checked.
i=0: (A, A, B) -> (A, B) with count=2
^ checked
i=1: (A, B) -> (A, B) with count=2
^ checked (B, not A!)
i=2: (doesn't occur because i < count is false)
This leaves the second A in the array with count=2, but the rose_neigh
structure has been freed. Code that accesses these entries assumes that
the first `count` entries are valid pointers, causing a use-after-free
when it accesses the dangling pointer.
Fix both issues by iterating over the array in reverse order with a fixed
loop bound. This ensures that all entries are examined and that the removal
of an entry doesn't affect subsequent iterations.28dCVE-2023-52849—14.3%
——4——CVE-2025-49431—14.3%
——4——CVE-2025-48147—14.3%
——4——CVE-2023-30083—14.3%
——4——CVE-2024-46654—14.3%
——4——CVE-2025-63064—14.3%
——4——CVE-2026-20258—14.3%
——4——CVE-2024-53180—14.3%
——4——CVE-2025-54970—14.3%
——4——CVE-2024-38554—14.3%
——4——CVE-2021-47053—14.3%
——4——CVE-2025-52599—14.3%
——4——CVE-2024-32793—14.3%
——4——CVE-2026-3567—14.3%
——4——CVE-2021-47052—14.3%
——4——CVE-2025-59270—14.3%
——4——CVE-2026-425066.1 MED14.3%
——4Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering.35dCVE-2024-45025—14.3%
——4——CVE-2024-32445—14.3%
——4——CVE-2024-53175—14.3%
——4——CVE-2025-63066—14.3%
——4——CVE-2026-22625—14.3%
——4——CVE-2025-61308—14.3%
——4——CVE-2021-47514—14.3%
——4——CVE-2024-35369—14.3%
——4——CVE-2025-61310—14.3%
——4——CVE-2025-43992—14.3%
——4——CVE-2025-22360—14.3%
——4——CVE-2025-61305—14.3%
——4——CVE-2024-48239—14.3%
——4——CVE-2025-47326—14.3%
——4——CVE-2026-575115.4 MED14.3%
——4SuperPlane before 0.30.0 contains an SMTP header injection vulnerability that allows unauthenticated attackers to inject arbitrary SMTP headers by including CRLF sequences in the event payload title field delivered via webhook. Attackers can manipulate the unsanitized title field passed to the SMTP DATA command to add Bcc recipients for content exfiltration, forge the From address to bypass SPF and DKIM checks, or inject Content-Type and MIME boundary headers to corrupt message bodies for phishing.28dCVE-2021-0328—14.3%
——4——CVE-2021-47007—14.3%
——4——CVE-2025-43206—14.3%
——4——CVE-2024-26765—14.3%
——4——CVE-2021-47008—14.3%
——4——CVE-2023-52848—14.3%
——4——CVE-2025-32780—14.3%
——4——