Vulnerabilidades exploráveis hoje
413,612na 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,740
- Alta22,744
- Média21,227
- Baixa2,176
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-30821—97.1%
——29——CVE-2003-0567—97.0%
——29——CVE-2019-8042—97.1%
——29——CVE-2014-4133—97.1%
——29——CVE-2023-25234—97.1%
——29——CVE-2012-2131—97.1%
——29——CVE-2025-43564—97.1%
——29——CVE-2014-1568—97.1%
——29——CVE-2020-29227—97.1%
——29——CVE-2007-0939—97.1%
——29——CVE-2022-435517.5 ALT97.1%
——29A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop (U+002E) `.`. Then in a subsequent request, it does not detect the HSTS state and makes a clear text transfer. Because it would store the info IDN encoded but look for it IDN decoded.29dCVE-2006-3657—97.1%
——29——CVE-2014-8176—97.1%
——29——CVE-2024-38197—97.1%
——29——CVE-2008-2167—97.1%
——29——CVE-2020-0881—97.1%
——29——CVE-2012-0145—97.1%
——29——CVE-2015-1791—97.1%
——29——CVE-2007-0674—97.1%
——29——CVE-2009-0065—97.1%
——29——CVE-2011-2750—97.1%
——29——CVE-2020-5307—97.1%
——29——CVE-2017-56477.5 ALT97.1%
——29A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C.10dCVE-2000-1221—97.1%
——29——CVE-2011-0660—97.1%
——29——CVE-2002-1795—97.1%
——29——CVE-2017-16849—97.1%
——29——CVE-1999-0224—97.1%
——29——CVE-2024-6931—97.1%
——29——CVE-2008-1558—97.1%
——29——CVE-2009-0263—97.1%
——29——CVE-2016-4438—97.1%
——29——CVE-2012-6554—97.1%
——29——CVE-2023-47207—97.0%
——29——CVE-2019-16123—97.1%
——29——CVE-2025-43563—97.1%
——29——CVE-2019-3778—97.1%
——29——CVE-2023-5322—97.1%
——29——CVE-2011-1893—97.1%
——29——CVE-2024-8669—97.1%
——29——