Vulnerabilidades exploráveis hoje
413,525na 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,739
- Alta22,705
- Média21,204
- Baixa2,175
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2022-3842—97.3%
——29——CVE-2004-1096—97.3%
——29——CVE-2013-0093—97.3%
——29——CVE-2003-0500—97.3%
——29——CVE-1999-1132—97.3%
——29——CVE-2023-27857—97.3%
——29——CVE-2018-5701—97.3%
——29——CVE-2001-0018—97.3%
——29——CVE-2012-4781—97.3%
——29——CVE-2019-9881—97.3%
——29——CVE-2023-4481—97.3%
——29——CVE-2015-6160—97.3%
——29——CVE-2012-5204—97.3%
——29——CVE-2003-0224—97.3%
——29——CVE-2020-9376—97.3%
——29——CVE-2016-7230—97.3%
——29——CVE-2014-1811—97.3%
——29——CVE-2018-8500—97.3%
——29——CVE-2002-0650—97.3%
——29——CVE-2021-34507.4 ALT97.3%
——29The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a "purpose" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named "purpose" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).34dCVE-2019-1124—97.3%
——29——CVE-2010-2563—97.3%
——29——CVE-2023-25610—97.3%
——29——CVE-2010-0434—97.3%
——29——CVE-2020-25787—97.3%
——29——CVE-2017-85098.8 ALT97.3%
——29A remote code execution vulnerability exists in Microsoft Office when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-8510, CVE-2017-8511, CVE-2017-8512, CVE-2017-0260, and CVE-2017-8506.28dCVE-2006-3660—97.3%
——29——CVE-2012-1849—97.3%
——29——CVE-2026-227789.8 CRÍ97.3%
——29vLLM is an inference and serving engine for large language models (LLMs). From 0.8.3 to before 0.14.1, when an invalid image is sent to vLLM's multimodal endpoint, PIL throws an error. vLLM returns this error to the client, leaking a heap address. With this leak, we reduce ASLR from 4 billion guesses to ~8 guesses. This vulnerability can be chained a heap overflow with JPEG2000 decoder in OpenCV/FFmpeg to achieve remote code execution. This vulnerability is fixed in 0.14.1.120dCVE-2021-27178—97.3%
——29——CVE-2015-1767—97.3%
——29——CVE-2014-9427—97.3%
——29——CVE-2013-0087—97.3%
——29——CVE-2010-5312—97.3%
——29——CVE-2014-3510—97.3%
——29——CVE-2001-0237—97.3%
——29——CVE-2015-1283—97.3%
——29——CVE-2022-40624—97.3%
——29——CVE-2014-6041—97.3%
——29——CVE-2021-22875—97.3%
——29——