Vulnerabilidades exploráveis hoje
4,383na 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,768
Novos KEV · 24H0
Exploit Today ≥ 701,700
Distribuição · última janela
- Crítica5,784
- Alta22,605
- Média22,024
- Baixa2,187
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2020-12027—99.0%
——30——CVE-2019-0808—99.0%
KEV—80Microsoft Win32k Privilege Escalation Vulnerability—CVE-2021-38147—99.0%
——30——CVE-2009-1955—99.0%
——30——CVE-2015-2419—99.0%
KEV—80Microsoft Internet Explorer Memory Corruption Vulnerability—CVE-2024-32964—99.0%
——30——CVE-2007-5099—99.0%
——30——CVE-2023-24078—99.0%
——30——CVE-2024-32238—99.0%
——30——CVE-2021-22160—99.0%
——30——CVE-2021-41381—99.0%
——30——CVE-2002-0150—99.0%
——30——CVE-2024-3922—99.0%
——30——CVE-2024-38023—99.0%
——30——CVE-2007-5348—99.0%
——30——CVE-2020-29279—99.0%
——30——CVE-2019-10097—99.0%
——30——CVE-2005-3589—99.0%
——30——CVE-2001-0538—99.0%
——30——CVE-2009-0557—99.0%
KEV—80Microsoft Office Object Record Corruption Vulnerability—CVE-2009-3591—99.0%
——30——CVE-2017-18017—99.0%
——30——CVE-2020-13382—99.0%
——30——CVE-2007-4921—99.0%
——30——CVE-2000-0457—99.0%
——30——CVE-2021-31213—99.0%
——30——CVE-2018-7286—99.0%
——30——CVE-2019-3964—99.0%
——30——CVE-2019-3963—99.0%
——30——CVE-2022-31470—99.0%
——30——CVE-2022-37436—99.0%
——30——CVE-2020-24435—99.0%
——30——CVE-2008-2370—99.0%
——30——CVE-2012-5691—99.0%
——30——CVE-2020-27615—99.0%
——30——CVE-2021-43778—99.0%
——30——CVE-2024-39931—99.0%
——30——CVE-2010-14287.5 ALT99.0%
KEVR80Red Hat JBoss Information Disclosure Vulnerability35dCVE-2022-31126—99.0%
——30——CVE-2020-139434.3 MÉD99.0%
——30If an HTTP/2 client connecting to Apache Tomcat 10.0.0-M1 to 10.0.0-M7, 9.0.0.M1 to 9.0.37 or 8.5.0 to 8.5.57 exceeded the agreed maximum number of concurrent streams for a connection (in violation of the HTTP/2 protocol), it was possible that a subsequent request made on that connection could contain HTTP headers - including HTTP/2 pseudo headers - from a previous request rather than the intended headers. This could lead to users seeing responses for unexpected resources.28d