Vulnerabilidades exploráveis hoje
409,857na visualização atual
Score único que combina CVSS, presença no KEV e EPSS. Cada CVE com sua própria ficha — timeline da publicação até a exploração ativa.
No catálogo KEV1,769
Novos KEV · 24H0
Exploit Today ≥ 701,700
Distribuição · última janela
- Crítica5,526
- Alta21,042
- Média20,196
- Baixa2,086
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2013-1391—99.5%
——30——CVE-2021-213466.1 MÉD99.5%
——30XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.32dCVE-2021-39843—99.5%
——30——CVE-2023-48085—99.5%
——30——CVE-2010-3275—99.5%
——30——CVE-2022-42424—99.5%
——30——CVE-2021-21667—99.5%
——30——CVE-2017-9554—99.5%
——30——CVE-2024-8504—99.5%
——30——CVE-2010-2550—99.5%
——30——CVE-2017-17850—99.5%
——30——CVE-2002-1643—99.5%
——30——CVE-2020-28347—99.5%
——30——CVE-2016-1542—99.5%
——30——CVE-2019-13345—99.5%
——30——CVE-2016-1561—99.5%
——30——CVE-2022-23642—99.5%
——30——CVE-2017-8046—99.5%
——30——CVE-2023-32167—99.5%
——30——CVE-1999-0128—99.5%
——30——CVE-2010-3653—99.5%
——30——CVE-2020-12109—99.5%
——30——CVE-2025-8943—99.5%
——30——CVE-2019-10267—99.5%
——30——CVE-2015-3087—99.5%
——30——CVE-2015-1592—99.5%
——30——CVE-2018-5378—99.5%
——30——CVE-2006-3942—99.5%
——30——CVE-2015-0779—99.5%
——30——CVE-2019-20215—99.5%
——30——CVE-2019-1234—99.5%
——30——CVE-2013-0803—99.5%
——30——CVE-2021-330375.3 MÉD99.5%
——30Apache Tomcat 10.0.0-M1 to 10.0.6, 9.0.0.M1 to 9.0.46 and 8.5.0 to 8.5.66 did not correctly parse the HTTP transfer-encoding request header in some circumstances leading to the possibility to request smuggling when used with a reverse proxy. Specifically: - Tomcat incorrectly ignored the transfer encoding header if the client declared it would only accept an HTTP/1.0 response; - Tomcat honoured the identify encoding; and - Tomcat did not ensure that, if present, the chunked encoding was the final encoding.30dCVE-2019-11248—99.5%
——30——CVE-2020-12124—99.5%
——30——CVE-2025-154678.8 ALT99.5%
——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.24dCVE-2013-7390—99.5%
——30——CVE-2001-0925—99.5%
——30——CVE-2001-0550—99.5%
——30——CVE-2025-30208—99.5%
——30——