Vulnerabilidades explotables hoy
414,707en 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,779
Nuevos KEV · 24H0
Exploit Today ≥ 701,707
Distribución · última ventana
- Crítico5,433
- Alto21,693
- Medio20,021
- Bajo2,091
Filtros
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2020-25901—92.5%
——28——CVE-2004-2081—92.5%
——28——CVE-2004-0238—92.5%
——28——CVE-2006-2413—92.5%
——28——CVE-2011-1264—92.5%
——28——CVE-2006-1935—92.5%
——28——CVE-2019-15092—92.5%
——28——CVE-2009-0145—92.5%
——28——CVE-2020-12856—92.5%
——28——CVE-2021-22510—92.5%
——28——CVE-2024-36728—92.5%
——28——CVE-2024-21433—92.5%
——28——CVE-2024-3191—92.5%
——28——CVE-2006-3582—92.5%
——28——CVE-2006-1023—92.5%
——28——CVE-2018-16850—92.5%
——28——CVE-2005-0780—92.5%
——28——CVE-2018-2815—92.5%
——28——CVE-2024-41319—92.5%
——28——CVE-2021-345297.8 ALT92.5%
——28Visual Studio Code Remote Code Execution Vulnerability95dCVE-2020-14305—92.5%
——28——CVE-2024-34950—92.5%
——28——CVE-2026-74820—92.5%
——28ServiceNow has remediated a SQL injection vulnerability that was identified in in the ServiceNow AI platform. This vulnerability could enable an unauthenticated user, in certain circumstances, to execute arbitrary SQL statements against the instance's underlying database and gain access to, or modify, instance data beyond what was intended.
ServiceNow deployed a security update to hosted instances and ServiceNow provided the update to our partners and self-hosted customers. We are not currently aware of malicious exploitation against ServiceNow instances.
We recommend customers promptly apply appropriate updates or upgrade to a patched release if they have not already done so.73dCVE-2007-4471—92.5%
——28——CVE-2008-1930—92.5%
——28——CVE-2020-28910—92.5%
——28——CVE-2021-46784—92.5%
——28——CVE-2013-2434—92.5%
——28——CVE-2010-2313—92.5%
——28——CVE-2016-3705—92.5%
——28——CVE-2023-46290—92.5%
——28——CVE-2021-37704—92.5%
——28——CVE-2022-322219.8 CRÍ92.5%
——28When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously was used to issue a `PUT` request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the subsequent `POST` request. The problem exists in the logic for a reused handle when it is changed from a PUT to a POST.30dCVE-2021-31641—92.5%
——28——CVE-2016-10087—92.5%
——28——CVE-2022-39285—92.5%
——28——CVE-2001-0649—92.5%
——28——CVE-2015-3250—92.5%
——28——CVE-2024-21646—92.5%
——28——CVE-2019-16889—92.5%
——28——