Vulnerabilidades exploráveis hoje
413,805na 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,594
- Alta22,456
- Média20,780
- Baixa2,126
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2009-2473—95.1%
——29——CVE-2020-15422—95.1%
——29——CVE-2016-4112—95.1%
——29——CVE-2012-0129—95.1%
——29——CVE-2026-26263—95.1%
——29——CVE-2001-0385—95.0%
——29——CVE-2018-8351—95.1%
——29——CVE-2016-4115—95.1%
——29——CVE-2016-3093—95.1%
——29——CVE-2022-24900—95.1%
——29——CVE-2018-16011—95.1%
——29——CVE-2018-0304—95.1%
——29——CVE-2008-5823—95.1%
——29——CVE-2023-51091—95.1%
——29——CVE-2000-0198—95.1%
——29——CVE-2016-0281—95.1%
——29——CVE-2022-257628.6 ALT95.1%
——29If a web application sends a WebSocket message concurrently with the WebSocket connection closing when running on Apache Tomcat 8.5.0 to 8.5.75 or Apache Tomcat 9.0.0.M1 to 9.0.20, it is possible that the application will continue to use the socket after it has been closed. The error handling triggered in this case could cause the a pooled object to be placed in the pool twice. This could result in subsequent connections using the same object concurrently which could result in data being returned to the wrong use and/or other errors.35dCVE-2015-8566—95.1%
——29——CVE-2010-4181—95.1%
——29——CVE-2003-0795—95.1%
——29——CVE-2009-2110—95.1%
——29——CVE-2009-1726—95.1%
——29——CVE-2005-1175—95.1%
——29——CVE-2025-5113—95.1%
——29——CVE-2018-11133—95.1%
——29——CVE-2024-39759—95.1%
——29——CVE-2006-0644—95.1%
——29——CVE-2001-0045—95.1%
——29——CVE-2013-3353—95.1%
——29——CVE-2010-4056—95.1%
——29——CVE-2015-7571—95.1%
——29——CVE-2007-1308—95.1%
——29——CVE-2017-11257—95.1%
——29——CVE-2013-4316—95.1%
——29——CVE-2007-6148—95.1%
——29——CVE-2021-42670—95.1%
——29——CVE-2013-3356—95.1%
——29——CVE-2020-15435—95.1%
——29——CVE-2023-40077—95.1%
——29——CVE-2023-4112—95.1%
——29——