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-2014-2863—91.2%
——27——CVE-2012-2316—91.2%
——27——CVE-2022-3699—91.2%
——27——CVE-2020-17383—91.2%
——27——CVE-2016-0945—91.2%
——27——CVE-2020-28035—91.2%
——27——CVE-2017-5539—91.2%
——27——CVE-2017-13865—91.2%
——27——CVE-2017-12796—91.2%
——27——CVE-2001-1332—91.2%
——27——CVE-2021-39823—91.2%
——27——CVE-2022-31692—91.2%
——27——CVE-2008-0616—91.2%
——27——CVE-2025-64368.1 ALT91.2%
——27Memory safety bugs present in Firefox 139 and Thunderbird 139. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability was fixed in Firefox 140 and Thunderbird 140.47dCVE-2017-6616—91.2%
——27——CVE-2007-6367—91.2%
——27——CVE-2018-8960—91.2%
——27——CVE-2016-5257—91.2%
——27——CVE-2017-2353—91.2%
——27——CVE-2020-11927.8 ALT91.2%
——27A remote code execution vulnerability exists in Visual Studio Code when the Python extension loads workspace settings from a notebook file. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
To exploit this vulnerability, an attacker would need to convince a target to open a specially crafted file in Visual Studio Code with the Python extension installed.
The update address the vulnerability by modifying the way Visual Studio Code Python extension enforces user settings.89dCVE-2012-1259—91.2%
——27——CVE-2016-4591—91.2%
——27——CVE-2004-1442—91.2%
——27——CVE-2021-44716—91.2%
——27——CVE-2012-2277—91.2%
——27——CVE-2016-2539—91.2%
——27——CVE-2012-5581—91.2%
——27——CVE-2017-7318—91.2%
——27——CVE-2016-0944—91.2%
——27——CVE-2010-2863—91.2%
——27——CVE-2005-0546—91.2%
——27——CVE-2020-22079—91.2%
——27——CVE-2015-8236—91.2%
——27——CVE-2017-15613—91.2%
——27——CVE-2025-29809—91.2%
——27——CVE-2009-3466—91.2%
——27——CVE-2018-10102—91.2%
——27——CVE-2016-0946—91.2%
——27——CVE-2016-0942—91.2%
——27——CVE-2020-29474—91.2%
——27——