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,489
- High15,874
- Medium14,811
- Low1,461
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2018-0758—99.6%
——30——CVE-2023-43177—99.6%
——30——CVE-2013-4212—99.6%
——30——CVE-2016-8870—99.6%
——30——CVE-2023-46263—99.6%
——30——CVE-2020-27868—99.6%
——30——CVE-2015-7766—99.6%
——30——CVE-2021-38540—99.6%
——30——CVE-2007-6203—99.6%
——30——CVE-2024-2876—99.6%
——30——CVE-2020-7136—99.6%
——30——CVE-2004-02305.0 NO 99.6%
——30TCP, when using a large Window Size, makes it easier for remote attackers to guess sequence numbers and cause a denial of service (connection loss) to persistent TCP connections by repeatedly injecting a TCP RST packet, especially in protocols that use long-lived connections, such as BGP.12dCVE-2020-262586.3 MED99.6%
——30XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.15, a Server-Side Forgery Request vulnerability can be activated when unmarshalling. The vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.15. The reported vulnerability does not exist if running Java 15 or higher. No user is affected who followed the recommendation to setup XStream's Security Framework with a whitelist! Anyone relying on XStream's default blacklist can immediately switch to a whilelist for the allowed types to avoid the vulnerability. Users of XStream 1.4.14 or below who still want to use XStream default blacklist can use a workaround described in more detailed in the referenced advisories.14dCVE-2019-1003002—99.6%
——30——CVE-2019-7254—99.6%
——30——CVE-2022-38418—99.6%
——30——CVE-2021-33543—99.6%
——30——CVE-2020-7200—99.6%
——30——CVE-2022-31704—99.6%
——30——CVE-2021-30128—99.6%
——30——CVE-2021-20034—99.6%
——30——CVE-2017-10974—99.6%
——30——CVE-2014-3829—99.6%
——30——CVE-2022-25148—99.6%
——30——CVE-2009-1185—99.6%
——30——CVE-2015-3827—99.6%
——30——CVE-2016-5734—99.6%
——30——CVE-2016-2098—99.6%
——30——CVE-2018-12464—99.6%
——30——CVE-2023-34992—99.6%
——30——CVE-2018-5955—99.6%
——30——CVE-2025-21298—99.6%
——30——CVE-2017-8779—99.6%
——30——CVE-2022-36958—99.6%
——30——CVE-2021-4104—99.6%
——30——CVE-2017-0290—99.6%
——30——CVE-2010-0805—99.6%
——30——CVE-2023-24488—99.6%
——30——CVE-2019-17602—99.6%
——30——CVE-2022-40770—99.6%
——30——