Vulnerabilities exploitable today
401,106in 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,754
New KEV · 24H0
Exploit Today ≥ 701,665
Distribution · last window
- Critical3,443
- High15,711
- Medium14,729
- Low1,450
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2009-2936—99.2%
——30——CVE-2007-1689—99.2%
——30——CVE-2023-44350—99.2%
——30——CVE-2011-3322—99.2%
——30——CVE-2008-4779—99.2%
——30——CVE-2022-4830—99.2%
——30——CVE-2009-1978—99.2%
——30——CVE-2021-36754—99.2%
——30——CVE-2017-11764—99.2%
——30——CVE-2007-2939—99.2%
——30——CVE-2007-3325—99.2%
——30——CVE-2021-40865—99.2%
——30——CVE-2024-8522—99.2%
——30——CVE-2023-1578—99.2%
——30——CVE-2012-1493—99.2%
——30——CVE-2017-16944—99.2%
——30——CVE-2026-0740—99.2%
——30——CVE-2020-28429—99.2%
——30——CVE-2004-0380—99.2%
——30——CVE-2024-46506—99.2%
——30——CVE-2021-34495.9 MED99.2%
——30An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to a crash and a denial of service attack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which is the default configuration). OpenSSL TLS clients are not impacted by this issue. All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j).13dCVE-2009-4444—99.2%
——30——CVE-2022-25772—99.2%
——30——CVE-2019-13396—99.2%
——30——CVE-2012-0299—99.2%
——30——CVE-2018-3191—99.2%
——30——CVE-2023-42442—99.2%
——30——CVE-2024-13179—99.2%
——30——CVE-2025-46618—99.2%
——30——CVE-2000-08847.5 NO 99.2%
——30IIS 4.0 and 5.0 allows remote attackers to read documents outside of the web root, and possibly execute arbitrary commands, via malformed URLs that contain UNICODE encoded characters, aka the "Web Server Folder Traversal" vulnerability.28dCVE-2020-28328—99.2%
——30——CVE-2005-1323—99.2%
——30——CVE-2014-3789—99.2%
——30——CVE-2019-15043—99.2%
——30——CVE-2023-5652—99.2%
——30——CVE-2021-229018.1 HIG99.2%
——30curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session ticket arrives over a connection. A malicious server can use this in rare unfortunate circumstances to potentially reach remote code execution in the client. When libcurl at run-time sets up support for TLS 1.3 session tickets on a connection using OpenSSL, it stores pointers to the transfer in-memory object for later retrieval when a session ticket arrives. If the connection is used by multiple transfers (like with a reused HTTP/1.1 connection or multiplexed HTTP/2 connection) that first transfer object might be freed before the new session is established on that connection and then the function will access a memory buffer that might be freed. When using that memory, libcurl might even call a function pointer in the object, making it possible for a remote code execution if the server could somehow manage to get crafted memory content into the correct place in memory.7dCVE-2021-21801—99.2%
——30——CVE-2014-1773—99.2%
——30——CVE-2018-8617—99.2%
——30——CVE-2018-8735—99.2%
——30——