Vulnerabilidades exploráveis hoje
413,655na 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,779
Novos KEV · 24H0
Exploit Today ≥ 701,707
Distribuição · última janela
- Crítica5,631
- Alta22,523
- Média21,014
- Baixa2,144
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2021-32099—96.3%
——29——CVE-2020-144225.9 MÉD96.3%
——29Lib/ipaddress.py in Python through 3.8.3 improperly computes hash values in the IPv4Interface and IPv6Interface classes, which might allow a remote attacker to cause a denial of service if an application is affected by the performance of a dictionary containing IPv4Interface or IPv6Interface objects, and this attacker can cause many dictionary entries to be created. This is fixed in: v3.5.10, v3.5.10rc1; v3.6.12; v3.7.9; v3.8.4, v3.8.4rc1, v3.8.5, v3.8.6, v3.8.6rc1; v3.9.0, v3.9.0b4, v3.9.0b5, v3.9.0rc1, v3.9.0rc2.29dCVE-2018-1002202—96.3%
——29——CVE-2021-21251—96.3%
——29——CVE-2013-0804—96.3%
——29——CVE-2007-6638—96.3%
——29——CVE-2004-0716—96.3%
——29——CVE-2021-26723—96.3%
——29——CVE-1999-0977—96.3%
——29——CVE-2018-9845—96.3%
——29——CVE-2015-6056—96.3%
——29——CVE-1999-1063—96.3%
——29——CVE-2014-0311—96.3%
——29——CVE-2014-1767—96.3%
——29——CVE-2005-3539—96.3%
——29——CVE-2015-5473—96.3%
——29——CVE-2023-40507.5 ALT96.3%
——29In some cases, an untrusted input stream was copied to a stack buffer without checking its size. This resulted in a potentially exploitable crash which could have led to a sandbox escape. This vulnerability affects Firefox < 116, Firefox ESR < 102.14, and Firefox ESR < 115.1.20dCVE-2013-5048—96.3%
——29——CVE-2017-1002002—96.3%
——29——CVE-2016-3384—96.3%
——29——CVE-2019-1208—96.3%
——29——CVE-2015-6050—96.3%
——29——CVE-2013-3880—96.3%
——29——CVE-2017-14097—96.3%
——29——CVE-2025-127629.1 CRÍ96.3%
——29pgAdmin versions up to 9.9 are affected by a Remote Code Execution (RCE) vulnerability that occurs when running in server mode and performing restores from PLAIN-format dump files. This issue allows attackers to inject and execute arbitrary commands on the server hosting pgAdmin, posing a critical risk to the integrity and security of the database management system and underlying data.25dCVE-2018-15138—96.3%
——29——CVE-2018-19861—96.3%
——29——CVE-2014-0298—96.3%
——29——CVE-2023-38667.5 ALT96.3%
——29In the Linux kernel, the following vulnerability has been resolved:
ksmbd: validate session id and tree id in the compound request
This patch validate session id and tree id in compound request.
If first operation in the compound is SMB2 ECHO request, ksmbd bypass
session and tree validation. So work->sess and work->tcon could be NULL.
If secound request in the compound access work->sess or tcon, It cause
NULL pointer dereferecing error.100dCVE-2018-4441—96.3%
——29——CVE-2019-16746—96.3%
——29——CVE-2023-34659—96.3%
——29——CVE-2024-28253—96.3%
——29——CVE-2019-1291—96.3%
——29——CVE-2019-1290—96.3%
——29——CVE-2010-1033—96.3%
——29——CVE-2014-5246—96.3%
——29——CVE-2008-0635—96.3%
——29——CVE-2024-38206—96.3%
——29——CVE-2024-91438.8 ALT96.3%
——29Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted
explicit values for the field polynomial can lead to out-of-bounds memory reads
or writes.
Impact summary: Out of bound memory writes can lead to an application crash or
even a possibility of a remote code execution, however, in all the protocols
involving Elliptic Curve Cryptography that we're aware of, either only "named
curves" are supported, or, if explicit curve parameters are supported, they
specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent
problematic input values. Thus the likelihood of existence of a vulnerable
application is low.
In particular, the X9.62 encoding is used for ECC keys in X.509 certificates,
so problematic inputs cannot occur in the context of processing X.509
certificates. Any problematic use-cases would have to be using an "exotic"
curve encoding.
The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(),
and various supporting BN_GF2m_*() functions.
Applications working with "exotic" explicit binary (GF(2^m)) curve parameters,
that make it possible to represent invalid field polynomials with a zero
constant term, via the above or similar APIs, may terminate abruptly as a
result of reading or writing outside of array bounds. Remote code execution
cannot easily be ruled out.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.3d