Vulnerabilities exploitable today
4,330in 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,748
New KEV · 24H0
Exploit Today ≥ 701,665
Distribution · last window
- Critical3,340
- High15,177
- Medium14,103
- Low1,353
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2017-8734—99.0%
——30——CVE-2010-1157—99.0%
——30——CVE-2022-26148—99.0%
——30——CVE-2021-35592—99.0%
——30——CVE-2012-5192—99.0%
——30——CVE-2024-41163—99.0%
——30——CVE-2018-17281—99.0%
——30——CVE-2019-1367—99.0%
KEVR80Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability—CVE-2025-154678.8 HIG99.0%
——30Issue summary: Parsing CMS AuthEnvelopedData or EnvelopedData message with
maliciously crafted AEAD parameters can trigger a stack buffer overflow.
Impact summary: A stack buffer overflow may lead to a crash, causing Denial
of Service, or potentially remote code execution.
When parsing CMS (Auth)EnvelopedData structures that use AEAD ciphers such as
AES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is
copied into a fixed-size stack buffer without verifying that its length fits
the destination. An attacker can supply a crafted CMS message with an
oversized IV, causing a stack-based out-of-bounds write before any
authentication or tag verification occurs.
Applications and services that parse untrusted CMS or PKCS#7 content using
AEAD ciphers (e.g., S/MIME (Auth)EnvelopedData with AES-GCM) are vulnerable.
Because the overflow occurs prior to authentication, no valid key material
is required to trigger it. While exploitability to remote code execution
depends on platform and toolchain mitigations, the stack-based write
primitive represents a severe risk.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this
issue, as the CMS implementation is outside the OpenSSL FIPS module
boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue.
OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.5dCVE-2024-25115.9 MED99.0%
——30Issue summary: Some non-default TLS server configurations can cause unbounded
memory growth when processing TLSv1.3 sessions
Impact summary: An attacker may exploit certain server configurations to trigger
unbounded memory growth that would lead to a Denial of Service
This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is
being used (but not if early_data support is also configured and the default
anti-replay protection is in use). In this case, under certain conditions, the
session cache can get into an incorrect state and it will fail to flush properly
as it fills. The session cache will continue to grow in an unbounded manner. A
malicious client could deliberately create the scenario for this failure to
force a Denial of Service. It may also happen by accident in normal operation.
This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS
clients.
The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL
1.0.2 is also not affected by this issue.6dCVE-2021-20081—99.0%
——30——CVE-2025-32375—99.0%
——30——CVE-2023-35924—99.0%
——30——CVE-2016-0710—99.0%
——30——CVE-2008-3471—99.0%
——30——CVE-2007-3898—99.0%
——30——CVE-2021-36393—99.0%
——30——CVE-2017-5174—99.0%
——30——CVE-2007-4620—99.0%
——30——CVE-2012-4031—99.0%
——30——CVE-2024-9061—99.0%
——30——CVE-2020-27615—99.0%
——30——CVE-2019-8953—99.0%
——30——CVE-2012-0897—99.0%
——30——CVE-2016-2388—99.0%
KEV—80SAP NetWeaver Information Disclosure Vulnerability—CVE-2019-13272—99.0%
KEV—80Linux Kernel Improper Privilege Management Vulnerability—CVE-2015-0925—99.0%
——30——CVE-2021-33032—99.0%
——30——CVE-2022-35919—99.0%
——30——CVE-2021-21480—99.0%
——30——CVE-2019-7232—99.0%
——30——CVE-2022-365348.8 HIG99.0%
——30Super Flexible Software GmbH & Co. KG Syncovery 9 for Linux v9.47x and below was discovered to contain multiple remote code execution (RCE) vulnerabilities via the Job_ExecuteBefore and Job_ExecuteAfter parameters at post_profilesettings.php.104dCVE-2008-3013—99.0%
——30——CVE-2020-11547—99.0%
——30——CVE-2022-44792—98.9%
——30——CVE-2010-3585—98.9%
——30——CVE-2021-28114—98.9%
——30——CVE-2008-1898—98.9%
——30——CVE-2020-14841—98.9%
——30——CVE-2025-54782—98.9%
——30——