Vulnerabilidades exploráveis hoje
415,241na visualização atual
Score único que combina CVSS, presença no KEV e EPSS. Cada CVE com sua própria ficha — timeline da publicação até a exploração ativa.
No catálogo KEV1,781
Novos KEV · 24H0
Exploit Today ≥ 701,709
Distribuição · última janela
- Crítica5,111
- Alta20,050
- Média19,099
- Baixa2,034
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2015-8560—92.7%
——28——CVE-2002-0253—92.7%
——28——CVE-2017-3110—92.7%
——28——CVE-2009-4581—92.7%
——28——CVE-2014-6417—92.7%
——28——CVE-2023-4974—92.7%
——28——CVE-2014-9189—92.7%
——28——CVE-2006-1061—92.7%
——28——CVE-2025-11187—92.7%
——28——CVE-2015-8799—92.7%
——28——CVE-2001-03806.4 SEM92.7%
——28Crosscom/Olicom XLT-F running XL 80 IM Version 5.5 Build Level 2 allows a remote attacker SNMP read and write access via a default, undocumented community string 'ILMI'.38dCVE-2011-3620—92.7%
——28——CVE-2011-2428—92.7%
——28——CVE-2022-44673—92.7%
——28——CVE-2017-12762—92.7%
——28——CVE-2011-1207—92.7%
——28——CVE-2008-1501—92.7%
——28——CVE-2025-108146.3 MÉD92.7%
——28A vulnerability was determined in D-Link DIR-823X 240126/240802/250416. Affected by this vulnerability is an unknown functionality of the file /usr/sbin/goahead. This manipulation of the argument port causes command injection. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized.36dCVE-2020-12100—92.7%
——28——CVE-2016-8687—92.7%
——28——CVE-2004-0648—92.7%
——28——CVE-2019-99476.1 MÉD92.7%
——28An issue was discovered in urllib2 in Python 2.x through 2.7.16 and urllib in Python 3.x through 3.7.3. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the path component of a URL that lacks a ? character) followed by an HTTP header or a Redis command. This is similar to the CVE-2019-9740 query string issue. This is fixed in: v2.7.17, v2.7.17rc1, v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1, v3.5.8, v3.5.8rc1, v3.5.8rc2, v3.5.9; v3.6.10, v3.6.10rc1, v3.6.11, v3.6.11rc1, v3.6.12, v3.6.9, v3.6.9rc1; v3.7.4, v3.7.4rc1, v3.7.4rc2, v3.7.5, v3.7.5rc1, v3.7.6, v3.7.6rc1, v3.7.7, v3.7.7rc1, v3.7.8, v3.7.8rc1, v3.7.9.34dCVE-2016-6297—92.7%
——28——CVE-2011-2199—92.7%
——28——CVE-2018-15997—92.7%
——28——CVE-2017-13797—92.7%
——28——CVE-2021-33571—92.7%
——28——CVE-2007-5005—92.7%
——28——CVE-2016-3690—92.7%
——28——CVE-2018-0790—92.7%
——28——CVE-2020-11856—92.7%
——28——CVE-2025-4340—92.7%
——28——CVE-2013-0623—92.7%
——28——CVE-2013-4527—92.7%
——28——CVE-2002-0712—92.7%
——28——CVE-2021-24226—92.7%
——28——CVE-2024-38085—92.7%
——28——CVE-2006-6104—92.7%
——28——CVE-2019-1411—92.7%
——28——CVE-2020-21999—92.7%
——28——