Vulnerabilidades exploráveis hoje
413,612na 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,779
Novos KEV · 24H0
Exploit Today ≥ 701,707
Distribuição · última janela
- Crítica5,740
- Alta22,744
- Média21,227
- Baixa2,176
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2025-43563—97.1%
——29——CVE-2012-0144—97.1%
——29——CVE-2003-1275—97.1%
——29——CVE-2022-29904—97.1%
——29——CVE-2008-3362—97.1%
——29——CVE-2024-37732—97.1%
——29——CVE-2014-4133—97.1%
——29——CVE-2012-0017—97.1%
——29——CVE-2017-6182—97.1%
——29——CVE-2016-00257.3 ALT97.1%
——29Microsoft Word 2007 SP3, Office 2010 SP2, Word 2010 SP2, Word 2013 SP1, Word 2013 RT SP1, Office 2016, Word 2016, Word for Mac 2011, Word 2016 for Mac, Office Compatibility Pack SP3, Word Automation Services on SharePoint Server 2010 SP2, Word Automation Services on SharePoint Server 2013 SP1, Office Web Apps 2010 SP2, Office Web Apps Server 2013 SP1, and Office Online Server allow remote attackers to execute arbitrary code via a crafted Office document, aka "Microsoft Office Memory Corruption Vulnerability."28dCVE-2026-31816—97.1%
——29——CVE-2004-1324—97.1%
——29——CVE-2010-1494—97.1%
——29——CVE-2000-1221—97.1%
——29——CVE-2023-47207—97.0%
——29——CVE-2006-3657—97.1%
——29——CVE-2015-1791—97.1%
——29——CVE-2025-43564—97.1%
——29——CVE-2014-2087—97.1%
——29——CVE-2011-2750—97.1%
——29——CVE-2014-8176—97.1%
——29——CVE-2014-1568—97.1%
——29——CVE-2017-13067—97.1%
——29——CVE-2019-3778—97.1%
——29——CVE-2010-3225—97.1%
——29——CVE-2026-30821—97.1%
——29——CVE-2016-3390—97.1%
——29——CVE-2006-5171—97.1%
——29——CVE-2020-5307—97.1%
——29——CVE-2022-435517.5 ALT97.1%
——29A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop (U+002E) `.`. Then in a subsequent request, it does not detect the HSTS state and makes a clear text transfer. Because it would store the info IDN encoded but look for it IDN decoded.29dCVE-2015-2485—97.1%
——29——CVE-2002-1795—97.1%
——29——CVE-2016-4438—97.1%
——29——CVE-2011-1891—97.1%
——29——CVE-2011-0660—97.1%
——29——CVE-2007-3175—97.1%
——29——CVE-2016-0856—97.1%
——29——CVE-2013-0022—97.1%
——29——CVE-2009-0263—97.1%
——29——CVE-2007-0939—97.1%
——29——