Vulnerabilities exploitable today
356,659in 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,662
New KEV · 24H0
Exploit Today ≥ 701,605
Distribution · last window
- Critical2,532
- High10,669
- Medium6,832
- Low683
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2025-31202—8.0%
——2——CVE-2023-54194—8.0%
——2——CVE-2026-64564—8.0%
——2In the Linux kernel, the following vulnerability has been resolved:
sctp: don't free the ASCONF's own transport in DEL-IP processing
sctp_process_asconf() caches the transport the ASCONF chunk is processed
against in asconf->transport (== chunk->transport, set once in sctp_rcv()).
For an ASCONF located through its Address Parameter by
__sctp_rcv_asconf_lookup(), that cached transport corresponds to the
Address Parameter, which need not be the packet's source address.
sctp_process_asconf_param() rejects a DEL-IP for the packet source address
(ADDIP D8, SCTP_ERROR_DEL_SRC_IP), but nothing protects asconf->transport.
A single ASCONF can therefore carry, in order:
[Address Parameter L] [DEL-IP L] [DEL-IP 0.0.0.0]
where L differs from the source. The DEL-IP for L passes the D8 check and
calls sctp_assoc_rm_peer() on the transport that asconf->transport still
points at, freeing it (RCU-deferred). The following wildcard DEL-IP then
reuses the now-dangling asconf->transport in sctp_assoc_set_primary() and
sctp_assoc_del_nonprimary_peers(): set_primary() dereferences the freed
transport (->ipaddr, ->state) and plants the dangling pointer into
asoc->peer.primary_path / active_path, and del_nonprimary_peers(), keeping
only the pointer that is no longer on the list, removes every real
transport, leaving the association with a transport_count of 0 and
primary_path/active_path pointing at freed memory.
Reject a DEL-IP that targets the transport the ASCONF is being processed
against, mirroring the existing source-address guard, so the wildcard
branch can never reuse a freed transport.15hCVE-2024-26859—8.0%
——2——CVE-2023-3495—8.0%
——2——CVE-2025-10570—8.0%
——2——CVE-2025-2545—8.0%
——2——CVE-2025-32425—8.0%
——2——CVE-2026-40875—8.0%
——2——CVE-2026-178456.1 MED8.0%
——2Inappropriate implementation in CSS in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to inject arbitrary scripts or HTML (UXSS) via a crafted HTML page. (Chromium security severity: Medium)5dCVE-2024-27817—8.0%
——2——CVE-2025-66085—8.0%
——2——CVE-2021-34391—8.0%
——2——CVE-2025-69237—8.0%
——2——CVE-2024-41811—8.0%
——2——CVE-2023-53787—8.0%
——2——CVE-2025-12056—8.0%
——2——CVE-2025-2180—7.9%
——2——CVE-2022-28768—7.9%
——2——CVE-2026-8563—7.9%
——2——CVE-2026-112594.3 MED7.9%
——2Insufficient validation of untrusted input in Cast in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: Low)16dCVE-2026-33588—7.9%
——2——CVE-2024-57844—7.9%
——2——CVE-2026-48493—7.9%
——2——CVE-2026-156129.1 CRI7.9%
——2Logto bypasses OIDC nonce validation when the nonce claim is absent from the id_token, enabling replay of authentication tokens and weakening session-binding.12dCVE-2018-25377—7.9%
——2——CVE-2024-51534—7.9%
——2——CVE-2023-52771—7.9%
——2——CVE-2024-47006—7.9%
——2——CVE-2025-14347—7.9%
——2——CVE-2024-35557—7.9%
——2——CVE-2025-46285—7.9%
——2——CVE-2025-30040—7.9%
——2——CVE-2026-0662—7.9%
——2——CVE-2026-615024.3 MED7.9%
——2Rejetto HFS 3.0.0 through 3.2.0 accepts state-changing API requests via the GET method and exempts GET requests from its anti-CSRF header check. A remote attacker can perform administrative actions including account creation and configuration changes leading to code execution - by causing a logged-in administrator's browser to navigate to a crafted URL, or without any credentials against default installations when the attack originates from the server's own machine.25dCVE-2025-6681—7.9%
——2——CVE-2022-31643—7.9%
——2——CVE-2025-6692—7.9%
——2——CVE-2026-48488—7.9%
——2phpMyFAQ is an open source FAQ web application. Prior to version 4.1.4, attachment passwords are hashed using SHA-1, a cryptographically broken algorithm. SHA-1 has been vulnerable to collision attacks since 2017 (SHAttered). Version 4.1.4 fixes the issue.16dCVE-2024-42492—7.9%
——2——