Vulnerabilities exploitable today
402,527in 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,756
New KEV · 24H0
Exploit Today ≥ 701,669
Distribution · last window
- Critical4,214
- High17,454
- Medium16,143
- Low1,571
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2024-7855—97.2%
——29——CVE-2008-3957—97.2%
——29——CVE-2020-0995—97.2%
——29——CVE-2010-0254—97.2%
——29——CVE-2018-16364—97.2%
——29——CVE-2016-7283—97.2%
——29——CVE-2000-0544—97.2%
——29——CVE-2019-7139—97.2%
——29——CVE-2022-208667.4 HIG97.2%
——29A vulnerability in the handling of RSA keys on devices running Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to retrieve an RSA private key. This vulnerability is due to a logic error when the RSA key is stored in memory on a hardware platform that performs hardware-based cryptography. An attacker could exploit this vulnerability by using a Lenstra side-channel attack against the targeted device. A successful exploit could allow the attacker to retrieve the RSA private key. The following conditions may be observed on an affected device: This vulnerability will apply to approximately 5 percent of the RSA keys on a device that is running a vulnerable release of Cisco ASA Software or Cisco FTD Software; not all RSA keys are expected to be affected due to mathematical calculations applied to the RSA key. The RSA key could be valid but have specific characteristics that make it vulnerable to the potential leak of the RSA private key. If an attacker obtains the RSA private key, they could use the key to impersonate a device that is running Cisco ASA Software or Cisco FTD Software or to decrypt the device traffic. See the Indicators of Compromise section for more information on the detection of this type of RSA key. The RSA key could be malformed and invalid. A malformed RSA key is not functional, and a TLS client connection to a device that is running Cisco ASA Software or Cisco FTD Software that uses the malformed RSA key will result in a TLS signature failure, which means a vulnerable software release created an invalid RSA signature that failed verification. If an attacker obtains the RSA private key, they could use the key to impersonate a device that is running Cisco ASA Software or Cisco FTD Software or to decrypt the device traffic.74dCVE-2017-5789—97.2%
——29——CVE-2018-19627—97.2%
——29——CVE-2024-38366—97.2%
——29——CVE-2021-27171—97.2%
——29——CVE-2008-4258—97.2%
——29——CVE-2019-1462—97.2%
——29——CVE-2023-1669—97.2%
——29——CVE-2020-27019—97.2%
——29——CVE-2019-1468—97.2%
——29——CVE-2012-4992—97.2%
——29——CVE-2016-3289—97.2%
——29——CVE-2004-1287—97.2%
——29——CVE-2013-3917—97.2%
——29——CVE-2006-3311—97.2%
——29——CVE-2024-41107—97.2%
——29——CVE-2026-21876—97.2%
——29——CVE-2010-1955—97.2%
——29——CVE-2017-7308—97.2%
——29——CVE-2021-40651—97.2%
——29——CVE-2019-8046—97.2%
——29——CVE-2011-2189—97.2%
——29——CVE-2007-3554—97.2%
——29——CVE-2024-13129—97.2%
——29——CVE-2018-5007—97.2%
——29——CVE-2016-3367—97.2%
——29——CVE-2015-1697—97.2%
——29——CVE-2017-5177—97.2%
——29——CVE-2007-1117—97.2%
——29——CVE-2007-0463—97.2%
——29——CVE-2000-0491—97.2%
——29——CVE-2001-0053—97.2%
——29——