Vulnerabilities exploitable today
378,068in 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,716
New KEV · 24H0
Exploit Today ≥ 701,651
Distribution · last window
- Critical2,293
- High8,417
- Medium6,703
- Low757
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2001-0912—32.0%
——10——CVE-2024-31392—32.0%
——10——CVE-2019-4118—32.0%
——10——CVE-2023-1158—32.0%
——10——CVE-2023-37025—32.0%
——10——CVE-2021-1067—32.0%
——10——CVE-2024-46300—32.0%
——10——CVE-2023-29011—32.0%
——10——CVE-2019-20700—32.0%
——10——CVE-2024-40542—32.0%
——10——CVE-2005-0393—32.0%
——10——CVE-2009-0361—32.0%
——10——CVE-2021-0290—32.0%
——10——CVE-2026-727348.4 HIG32.0%
——10Dokploy is a free, self-hostable Platform as a Service (PaaS). From 0.28.7 until 0.29.13, the server.remove tRPC mutation in apps/dokploy/server/api/routers/server.ts accepts a caller-controlled serverId and calls haveActiveServices, findServerById, removeDeploymentsByServerId, and deleteServer without verifying that currentServer.organizationId equals ctx.session.activeOrganizationId. An authenticated owner or administrator with server:delete in one organization who previously observed another organization's serverId can delete that organization's server registration and deployment records, interrupt Dokploy management, and receive the associated plaintext SSH private key even though server.one denies the same cross-organization read. This issue is fixed in version 0.29.13.13dCVE-2024-32129—32.0%
——10——CVE-2025-26370—32.0%
——10——CVE-2024-1160—32.0%
——10——CVE-2025-60852—32.0%
——10——CVE-2026-638579.8 CRI32.0%
——10In the Linux kernel, the following vulnerability has been resolved:
net: airoha: Do not read uninitialized fragment address in airoha_dev_xmit()
The transmit loop in airoha_dev_xmit() reads fragment address and length
during its final iteration, when the loop index equals
skb_shinfo(skb)->nr_frags, at which point the fragment data is
uninitialized. While these values are never consumed, the read itself is
unsafe and may trigger a page fault. Fix this by avoiding the fragment
read on the last iteration.
Additionally, move the skb pointer from the first to the last used packet
descriptor, so that airoha_qdma_tx_napi_poll() defers freeing the skb
until the final descriptor is processed.56dCVE-2026-35194—32.0%
——10——CVE-2024-41816—32.0%
——10——CVE-2024-1159—32.0%
——10——CVE-2023-30963—32.0%
——10——CVE-2025-32971—32.0%
——10——CVE-2023-37031—32.0%
——10——CVE-2019-11137—32.0%
——10——CVE-2023-2228—32.0%
——10——CVE-2011-1745—32.0%
——10——CVE-2011-2022—32.0%
——10——CVE-2013-3233—32.0%
——10——CVE-2024-3576—32.0%
——10——CVE-2025-60316—32.0%
——10——CVE-2026-109558.8 HIG32.0%
——10Type Confusion in ANGLE in Google Chrome on Windows prior to 149.0.7827.53 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)61dCVE-2026-84459.8 CRI32.0%
——10justhtml versions <= 1.11.0 (fixed in 1.12.0) do not sufficiently escape HTML-significant characters (angle brackets) in text nodes when converting a parsed document to Markdown via to_markdown(). While a small set of Markdown metacharacters are escaped, characters such as < and > are preserved, so untrusted input that is safe in to_html() — including entity-decoded text (e.g. <script>) or text from RCDATA/RAWTEXT-parsed elements like <title>, <textarea>, <noscript>, and <plaintext> — can be emitted as raw HTML in the Markdown output, enabling a sanitizer bypass and potential cross-site scripting when that output is rendered.28dCVE-2025-2030—32.0%
——10——CVE-2025-55099—32.0%
——10——CVE-2024-34958—32.0%
——10——CVE-2022-30701—32.0%
——10——CVE-2019-16861—32.0%
——10——CVE-2022-31030—32.0%
——10——