Vulnerabilities exploitable today
407,531in 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,766
New KEV · 24H0
Exploit Today ≥ 701,698
Distribution · last window
- Critical5,704
- High22,182
- Medium20,667
- Low2,163
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-1999-0519—92.9%
——28——CVE-2017-12515—92.9%
——28——CVE-2003-0586—92.9%
——28——CVE-2014-9766—92.9%
——28——CVE-2015-3408—92.9%
——28——CVE-2017-12529—92.9%
——28——CVE-2017-12532—92.9%
——28——CVE-2017-12539—92.9%
——28——CVE-2015-0984—92.9%
——28——CVE-2017-12526—92.9%
——28——CVE-2017-12512—92.9%
——28——CVE-2017-12533—92.9%
——28——CVE-2017-12489—92.9%
——28——CVE-2018-16010—92.9%
——28——CVE-2015-0561—92.9%
——28——CVE-2017-12497—92.9%
——28——CVE-2005-20967.5 NO 92.9%
——28zlib 1.2 and later versions allows remote attackers to cause a denial of service (crash) via a crafted compressed stream with an incomplete code description of a length greater than 1, which leads to a buffer overflow, as demonstrated using a crafted PNG file.113dCVE-2015-480510.0 NO 92.9%
——28Unspecified vulnerability in Oracle Java SE 6u101, 7u85, and 8u60, and Java SE Embedded 8u51, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Serialization.20dCVE-2021-26600—92.9%
——28——CVE-2017-12508—92.9%
——28——CVE-2003-0803—92.9%
——28——CVE-2017-12495—92.9%
——28——CVE-2017-12527—92.9%
——28——CVE-2017-12510—92.9%
——28——CVE-2017-12501—92.9%
——28——CVE-1999-0116—92.9%
——28——CVE-2010-3565—92.9%
——28——CVE-2021-24295—92.9%
——28——CVE-2018-20727—92.9%
——28——CVE-2008-1185—92.9%
——28——CVE-2017-12535—92.9%
——28——CVE-2017-12513—92.9%
——28——CVE-2008-3684—92.9%
——28——CVE-2005-3304—92.9%
——28——CVE-2017-12503—92.9%
——28——CVE-2008-5272—92.9%
——28——CVE-2007-4902—92.9%
——28——CVE-2024-454315.3 MED92.9%
——28OpenSynergy BlueSDK (aka Blue SDK) through 6.x has Improper Input Validation. The specific flaw exists within the BlueSDK Bluetooth stack. The issue results from the lack of proper validation of remote L2CAP channel ID (CID). An attacker can leverage this to create an L2CAP channel with the null identifier assigned as a remote CID.7dCVE-2017-12498—92.9%
——28——CVE-2008-6563—92.9%
——28——