Vulnerabilities exploitable today
352,162in 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,653
New KEV · 24H0
Exploit Today ≥ 701,590
Distribution · last window
- Critical2,073
- High6,924
- Medium5,904
- Low547
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-2245—2.7%
——1——CVE-2026-41965—2.7%
——1——CVE-2026-42250—2.7%
——1——CVE-2026-46182—2.7%
——1——CVE-2024-52288—2.7%
——1——CVE-2023-25189—2.7%
——1——CVE-2026-26963—2.7%
——1——CVE-2023-41090—2.7%
——1——CVE-2026-3407—2.7%
——1——CVE-2026-43400—2.7%
——1——CVE-2026-22174—2.7%
——1——CVE-2026-53426—2.7%
——1Allocation of Resources Without Limits or Throttling vulnerability in leandrocp MDEx allows Excessive Allocation.
MDEx.parse_document/2 accepts a {:json, json} source. In lib/mdex.ex, the private json_to_node/1 function passes the attacker-controlled node_type value to Module.concat/1, which calls String.to_atom/1 and interns a brand-new atom for every distinct value. Atoms are never garbage collected on the BEAM, so a crafted JSON document carrying a unique node_type at each (deeply nested) node mints one permanent atom per node.
A single document can intern hundreds of thousands of atoms, and a large enough document exhausts the default atom table (around 1,048,576 atoms) and aborts the entire Erlang VM, taking down every process on the node. Any application that passes untrusted input to the {:json, ...} source of MDEx.parse_document is exposed to an unauthenticated denial-of-service.
This issue affects mdex from 0.4.3 before 0.13.2.23dCVE-2026-532745.5 MED2.7%
——1In the Linux kernel, the following vulnerability has been resolved:
net/smc: fix sleep-inside-lock in __smc_setsockopt() causing local DoS
A logic flaw in __smc_setsockopt() allows a local unprivileged user to
cause a Denial of Service (DoS) by holding the socket lock indefinitely.
The function __smc_setsockopt() calls copy_from_sockptr() while holding
lock_sock(sk). By passing a userfaultfd-monitored memory page (or
FUSE-backed memory on systems where unprivileged userfaultfd is disabled)
as the optval, an attacker can halt execution during the copy operation,
keeping the lock held.
Combined with asynchronous tear-down operations like shutdown(), this
exhausts the kernel wq (kworkers) and triggers the hung task watchdog.
[ 240.123456] INFO: task kworker/u8:2 blocked for more than 120 seconds.
[ 240.123489] Call Trace:
[ 240.123501] smc_shutdown+...
[ 240.123512] lock_sock_nested+...
This patch moves the user-space copy outside the lock_sock() critical
section to prevent the issue.15dCVE-2020-27057—2.7%
——1——CVE-2025-30431—2.7%
——1——CVE-2019-10486—2.7%
——1——CVE-2026-53429—2.7%
——1Missing Release of Memory after Effective Lifetime vulnerability in leandrocp mdex and mdex_native allows an attacker who controls a rendered document to cause a denial of service through unbounded native memory exhaustion.
The native rendering code permanently leaks memory when rendering a document that contains escaped-tag nodes. The conversion of each %MDEx.EscapedTag{} node into its native representation (From<ExEscapedTag> for NodeValue in the Rust NIF) calls Box::leak on the caller-supplied literal string, which surrenders the backing allocation so that it lives for the entire lifetime of the operating system process and is never freed.
Both the byte length of each literal and the number of escaped-tag nodes in a document are attacker-controlled, and there is no size cap, rate limit, or string interning on this path. Every render of a document containing escaped-tag nodes therefore leaks literal_size x node_count bytes that can never be reclaimed, and repeated renders accumulate without bound. Rendering reaches this path through the public MDEx.to_html/1 entry point and any other API that renders a supplied %MDEx.Document{}.
Any application that uses mdex (or mdex_native directly) to render documents derived from user-supplied content is affected. Because the leaked memory is never reclaimed for the life of the BEAM process, an attacker can drive resident memory upward without limit until the node exhausts memory and crashes, taking down every process on it.
The vulnerable native code originally shipped inside mdex (in native/comrak_nif/src/types/document.rs) and was later extracted into the separate mdex_native package (native/mdex_native_nif/src/types/document.rs), where it remains unpatched.
This issue affects mdex from 0.11.0 before 0.12.3, and mdex_native from 0.1.0 before 0.2.3.23dCVE-2018-25273—2.7%
——1——CVE-2024-35140—2.7%
——1——CVE-2026-43437—2.7%
——1——CVE-2025-20627—2.7%
——1——CVE-2025-6942—2.7%
——1——CVE-2022-22457—2.7%
——1——CVE-2025-36573—2.7%
——1——CVE-2021-0395—2.7%
——1——CVE-2026-31675—2.7%
——1——CVE-2025-20675—2.7%
——1——CVE-2025-11906—2.7%
——1——CVE-2024-34586—2.7%
——1——CVE-2025-36513—2.7%
——1——CVE-2019-20550—2.7%
——1——CVE-2025-13139—2.7%
——1——CVE-2026-34851—2.7%
——1——CVE-2025-69644—2.7%
——1——CVE-2025-2781—2.7%
——1——CVE-2025-38436—2.7%
——1——CVE-2026-55411—2.7%
——1——CVE-2024-8315—2.7%
——1——CVE-2024-55582—2.7%
——1——CVE-2026-1852—2.7%
——1——