Vulnerabilidades explotables hoy
404,880en la vista actual
Score único combinando CVSS, membresía KEV y EPSS. Cada CVE con su ficha propia — timeline desde publicación hasta explotación activa.
En catálogo KEV1,760
Nuevos KEV · 24H0
Exploit Today ≥ 701,693
Distribución · última ventana
- Crítico5,629
- Alto21,804
- Medio20,192
- Bajo2,115
Filtros
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2013-3520—99.0%
——30——CVE-2015-1397—99.0%
——30——CVE-2009-1430—99.0%
——30——CVE-2017-8635—99.0%
——30——CVE-2021-21745—99.0%
——30——CVE-2023-42327—99.0%
——30——CVE-2008-4008—99.0%
——30——CVE-2019-11229—99.0%
——30——CVE-2004-0594—99.0%
——30——CVE-2010-2115—99.0%
——30——CVE-2023-32169—99.0%
——30——CVE-2008-3008—99.0%
——30——CVE-2023-50223—99.0%
——30——CVE-2005-2551—99.0%
——30——CVE-2020-94847.0 ALT99.0%
——30When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server is configured to use the PersistenceManager with a FileStore; and c) the PersistenceManager is configured with sessionAttributeValueClassNameFilter="null" (the default unless a SecurityManager is used) or a sufficiently lax filter to allow the attacker provided object to be deserialized; and d) the attacker knows the relative file path from the storage location used by FileStore to the file the attacker has control over; then, using a specifically crafted request, the attacker will be able to trigger remote code execution via deserialization of the file under their control. Note that all of conditions a) to d) must be true for the attack to succeed.20dCVE-2019-7111—99.0%
——30——CVE-2020-139434.3 MED99.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.20dCVE-2015-8000—99.0%
——30——CVE-2018-1612—99.0%
——30——CVE-2014-9708—99.0%
——30——CVE-2025-2945—99.0%
——30——CVE-2023-41249—99.0%
——30——CVE-2023-0159—99.0%
——30——CVE-2024-38819—99.0%
——30——CVE-2021-25003—99.0%
——30——CVE-2010-1423—99.0%
——30——CVE-2019-7255—99.0%
——30——CVE-2015-1833—99.0%
——30——CVE-2025-6970—99.0%
——30——CVE-2022-24124—99.0%
——30——CVE-2006-1388—99.0%
——30——CVE-2024-45388—99.0%
——30——CVE-2003-0347—99.0%
——30——CVE-2008-2168—99.0%
——30——CVE-2023-50218—99.0%
——30——CVE-2021-39352—99.0%
——30——CVE-2013-0025—99.0%
——30——CVE-2017-11810—99.0%
——30——CVE-2013-5877—99.0%
——30——CVE-2023-32645—99.0%
——30——