Vulnerabilities exploitable today
374,073in 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,710
New KEV · 24H0
Exploit Today ≥ 701,645
Distribution · last window
- Critical2,342
- High8,459
- Medium6,415
- Low712
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2024-4580—25.8%
——8——CVE-2024-6870—25.8%
——8——CVE-2026-118107.5 HIG25.8%
——8The UpdateHub firmware-update agent's probe handler (z_impl_updatehub_probe() in subsys/mgmt/updatehub/updatehub.c) parses the JSON metadata returned by the update server into a fixed two-level nested-array struct. After parsing it validates only the outer array length (objects_len != 2) and then dereferences objects[1].objects[0].objects.sha256sum via strlen() without checking that the inner object array of element [1] is non-empty.
The metadata is attacker-influenceable network input: the agent fetches it over CoAP from the configured UpdateHub server during its routine OTA probe. A malicious or compromised update server (or, when DTLS is disabled, a network man-in-the-middle) can return a response whose second outer object array is empty. Because the parse target is zero-initialised, the corresponding objects[1].objects[0].objects.sha256sum pointer is NULL, and the subsequent strlen() dereferences address zero. The same defect exists in both the 'any boards' and 'some boards' metadata layouts.
The resulting CPU fault is fatal under Zephyr's default error handling, halting or resetting the device, so the flaw is a remotely triggerable denial of service. Impact is limited to availability; it is a read from NULL with no out-of-bounds write, memory corruption, or information disclosure. The fix rejects metadata whose inner object array is empty before any dereference, on both layouts.20dCVE-2025-46850—25.8%
——8——CVE-2024-50348—25.8%
——8——CVE-2026-24823—25.8%
——8——CVE-2026-850509.6 CRI25.8%
——8Out of bounds write in WebGL in Google Chrome on on Android prior to 152.0.7977.82 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)7dCVE-2006-6622—25.8%
——8——CVE-2011-0543—25.8%
——8——CVE-2024-12767—25.8%
——8——CVE-2026-25390—25.8%
——8——CVE-2026-25454—25.8%
——8——CVE-2025-4390—25.8%
——8——CVE-2023-30216—25.8%
——8——CVE-2025-46950—25.8%
——8——CVE-2025-46949—25.8%
——8——CVE-2023-30207—25.8%
——8——CVE-2025-46863—25.8%
——8——CVE-2024-38501—25.8%
——8——CVE-2015-1970—25.8%
——8——CVE-2026-29098—25.8%
——8——CVE-2023-1446—25.8%
——8——CVE-2023-43962—25.8%
——8——CVE-2022-31233—25.8%
——8——CVE-2026-48128—25.8%
——8——CVE-2024-28521—25.8%
——8——CVE-2025-28254—25.8%
——8——CVE-2025-46855—25.8%
——8——CVE-2021-43327—25.8%
——8——CVE-2025-54425—25.8%
——8——CVE-2025-27186—25.8%
——8——CVE-2026-807177.5 HIG25.8%
——8In the Linux kernel, the following vulnerability has been resolved:
sctp: validate Adaptation Indication parameter length
The Adaptation Layer Indication parameter contains a fixed 32-bit
Adaptation Code Point after its parameter header. However,
sctp_verify_param() accepts a header-only parameter because the generic
parameter walker only requires the header to be present.
sctp_process_param() then reads adaptation_ind beyond the declared
parameter. When the malformed parameter is last in an INIT, the read
starts at the receive skb tail, and the value is copied into the state
cookie returned in the INIT ACK. This may disclose four receive-buffer
tail bytes.
Require the declared parameter length to match the fixed structure size
and abort the association through the existing invalid parameter length
path otherwise.17dCVE-2024-6896—25.8%
——8——CVE-2024-12179—25.8%
——8——CVE-2026-340525.9 MED25.8%
——8LTI JupyterHub Authenticator is a JupyterHub authenticator for LTI. Prior to version 1.6.3, the LTI 1.1 validator stores OAuth nonces in a class-level dictionary that grows without bounds. Nonces are added before signature validation, so an attacker with knowledge of a valid consumer key can send repeated requests with unique nonces to gradually exhaust server memory, causing a denial of service. This issue has been patched in version 1.6.3.53dCVE-2025-5261—25.8%
——8——CVE-2004-1204—25.8%
——8——CVE-2021-24446—25.8%
——8——CVE-2014-0147—25.8%
——8——CVE-2010-10017—25.8%
——8——