Vulnerabilidades explotables hoy
414,984en 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,080
- Alto19,946
- Medio18,988
- Bajo2,018
Filtros
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2012-5006—91.2%
——27——CVE-2021-34992—91.2%
——27——CVE-2017-8684—91.2%
——27——CVE-2020-8137—91.2%
——27——CVE-2024-300917.8 ALT91.2%
——27Win32k Elevation of Privilege Vulnerability119dCVE-2015-9222—91.2%
——27——CVE-2020-6087—91.2%
——27——CVE-2014-5181—91.2%
——27——CVE-2017-12120—91.2%
——27——CVE-2014-2262—91.2%
——27——CVE-2025-544068.8 ALT91.2%
——27Multiple OS command injection vulnerabilities exist in the formPingCmd functionality of Planet WGR-500 v1.3411b190912. A specially crafted series of HTTP requests can lead to arbitrary command execution. An attacker can send a series of HTTP requests to trigger these vulnerabilities.This command injection is related to the `counts` request parameter.39dCVE-2008-3075—91.2%
——27——CVE-2021-34813—91.2%
——27——CVE-2024-30284—91.2%
——27——CVE-2022-45709—91.2%
——27——CVE-2005-1029—91.2%
——27——CVE-2015-3216—91.2%
——27——CVE-2016-2297—91.2%
——27——CVE-2017-7110—91.2%
——27——CVE-2002-1480—91.2%
——27——CVE-2021-228975.3 MED91.2%
——27curl 7.61.0 through 7.76.1 suffers from exposure of data element to wrong session due to a mistake in the code for CURLOPT_SSL_CIPHER_LIST when libcurl is built to use the Schannel TLS library. The selected cipher set was stored in a single "static" variable in the library, which has the surprising side-effect that if an application sets up multiple concurrent transfers, the last one that sets the ciphers will accidentally control the set used by all transfers. In a worst-case scenario, this weakens transport security significantly.33dCVE-2011-3003—91.2%
——27——CVE-2016-5040—91.2%
——27——CVE-2004-1196—91.2%
——27——CVE-2018-7082—91.2%
——27——CVE-2019-18643—91.2%
——27——CVE-2022-2711—91.2%
——27——CVE-2019-13954—91.2%
——27——CVE-2003-0416—91.2%
——27——CVE-2012-2127—91.2%
——27——CVE-2012-1175—91.2%
——27——CVE-2012-1124—91.2%
——27——CVE-2002-0676—91.2%
——27——CVE-2009-0042—91.2%
——27——CVE-2016-9936—91.2%
——27——CVE-2011-4558—91.2%
——27——CVE-2006-0789—91.2%
——27——CVE-2014-9664—91.2%
——27——CVE-2021-213536.8 MED91.2%
——27Pug is an npm package which is a high-performance template engine. In pug before version 3.0.1, if a remote attacker was able to control the `pretty` option of the pug compiler, e.g. if you spread a user provided object such as the query parameters of a request into the pug template inputs, it was possible for them to achieve remote code execution on the node.js backend. This is fixed in version 3.0.1. This advisory applies to multiple pug packages including "pug", "pug-code-gen". pug-code-gen has a backported fix at version 2.0.3. This advisory is not exploitable if there is no way for un-trusted input to be passed to pug as the `pretty` option, e.g. if you compile templates in advance before applying user input to them, you do not need to upgrade.14dCVE-2020-0198—91.2%
——27——