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-2021-22242—99.2%
——30——CVE-2024-26212—99.2%
——30——CVE-2004-0380—99.2%
——30——CVE-2025-4443—99.2%
——30——CVE-2024-47175—99.2%
——30——CVE-2022-25772—99.2%
——30——CVE-2004-0313—99.2%
——30——CVE-2019-15043—99.2%
——30——CVE-2023-50968—99.2%
——30——CVE-2023-42442—99.2%
——30——CVE-2022-23302—99.2%
——30——CVE-2006-5216—99.2%
——30——CVE-2002-2226—99.2%
——30——CVE-2024-8522—99.2%
——30——CVE-2009-4660—99.2%
——30——CVE-2023-1578—99.2%
——30——CVE-2018-9948—99.2%
——30——CVE-2006-5780—99.2%
——30——CVE-2008-0067—99.2%
——30——CVE-2004-1638—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-2004-0212—99.2%
——30——CVE-2023-26475—99.2%
——30——CVE-2016-0638—99.2%
——30——CVE-2007-3220—99.2%
——30——CVE-2025-6216810.0 CRI99.2%
——30Squid is a caching proxy for the Web. In Squid versions prior to 7.2, a failure to redact HTTP authentication credentials in error handling allows information disclosure. The vulnerability allows a script to bypass browser security protections and learn the credentials a trusted client uses to authenticate. This potentially allows a remote client to identify security tokens or credentials used internally by a web application using Squid for backend load balancing. These attacks do not require Squid to be configured with HTTP authentication. The vulnerability is fixed in version 7.2. As a workaround, disable debug information in administrator mailto links generated by Squid by configuring squid.conf with email_err_data off.2dCVE-2014-2323—99.2%
——30——CVE-2023-39473—99.2%
——30——CVE-2007-2708—99.2%
——30——CVE-2024-43642—99.2%
——30——CVE-2005-1812—99.2%
——30——CVE-2004-0798—99.2%
——30——CVE-2013-3307—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-2019-13396—99.2%
——30——CVE-2013-4822—99.2%
——30——CVE-2024-50340—99.2%
——30——CVE-2004-0964—99.2%
——30——CVE-2019-14205—99.2%
——30——