Vulnerabilidades explotables hoy
414,784en 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,781
Nuevos KEV · 24H0
Exploit Today ≥ 701,709
Distribución · última ventana
- Crítico5,284
- Alto20,832
- Medio19,524
- Bajo2,048
Filtros
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2005-0738—91.7%
——28——CVE-2011-2914—91.7%
——28——CVE-2019-0008—91.7%
——28——CVE-2019-8690—91.7%
——28——CVE-2020-3772—91.7%
——28——CVE-2021-391398.5 ALT91.7%
——28XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. A user is only affected if using the version out of the box with JDK 1.7u21 or below. However, this scenario can be adjusted easily to an external Xalan that works regardless of the version of the Java runtime. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.39dCVE-2008-2333—91.7%
——28——CVE-2006-0171—91.7%
——28——CVE-2018-14463—91.7%
——28——CVE-2016-4063—91.7%
——28——CVE-2002-1858—91.7%
——28——CVE-2018-0921—91.7%
——28——CVE-2018-0944—91.7%
——28——CVE-2021-229467.5 ALT91.7%
——28A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an IMAP, POP3 or FTP server (`--ssl-reqd` on the command line or`CURLOPT_USE_SSL` set to `CURLUSESSL_CONTROL` or `CURLUSESSL_ALL` withlibcurl). This requirement could be bypassed if the server would return a properly crafted but perfectly legitimate response.This flaw would then make curl silently continue its operations **withoutTLS** contrary to the instructions and expectations, exposing possibly sensitive data in clear text over the network.32dCVE-2020-3802—91.7%
——28——CVE-2012-3158—91.7%
——28——CVE-2018-0910—91.7%
——28——CVE-2020-3780—91.7%
——28——CVE-2015-5224—91.7%
——28——CVE-2020-3770—91.7%
——28——CVE-2006-2485—91.7%
——28——CVE-2008-3626—91.7%
——28——CVE-2014-9751—91.7%
——28——CVE-2014-6598—91.7%
——28——CVE-2005-2976—91.7%
——28——CVE-2023-52325—91.7%
——28——CVE-2015-5288—91.7%
——28——CVE-2013-2643—91.7%
——28——CVE-2011-2913—91.7%
——28——CVE-2018-0947—91.7%
——28——CVE-2017-3630—91.7%
——28——CVE-2018-0914—91.7%
——28——CVE-2010-0829—91.7%
——28——CVE-2014-0587—91.7%
——28——CVE-2016-6147—91.7%
——28——CVE-2024-39911—91.7%
——28——CVE-2014-0585—91.7%
——28——CVE-2020-5644—91.7%
——28——CVE-2018-0912—91.7%
——28——CVE-2012-2406—91.7%
——28——