Vulnerabilidades exploráveis hoje
419,076na 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,786
Novos KEV · 24H0
Exploit Today ≥ 701,715
Distribuição · última janela
- Crítica4,738
- Alta18,304
- Média18,049
- Baixa1,972
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2006-4164—86.7%
——26——CVE-2009-4175—86.7%
——26——CVE-2007-2663—86.7%
——26——CVE-2006-7017—86.7%
——26——CVE-2020-7634—86.7%
——26——CVE-2017-5944—86.7%
——26——CVE-2006-2074—86.7%
——26——CVE-2005-0347—86.7%
——26——CVE-2017-3104—86.7%
——26——CVE-2015-7098—86.7%
——26——CVE-2017-2830—86.7%
——26——CVE-2004-2239—86.7%
——26——CVE-2021-28544—86.7%
——26——CVE-2012-0503—86.7%
——26——CVE-2014-8316—86.7%
——26——CVE-2021-23463—86.7%
——26——CVE-2025-578226.5 MÉD86.7%
——26Next.js is a React framework for building full-stack web applications. Prior to versions 14.2.32 and 15.4.7, when next() was used without explicitly passing the request object, it could lead to SSRF in self-hosted applications that incorrectly forwarded user-supplied headers. This vulnerability has been fixed in Next.js versions 14.2.32 and 15.4.7. All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the next() function.33dCVE-2023-42628—86.7%
——26——CVE-2001-0051—86.7%
——26——CVE-2017-9354—86.7%
——26——CVE-2006-0597—86.7%
——26——CVE-2015-6465—86.7%
——26——CVE-2019-12414—86.7%
——26——CVE-2021-32976—86.7%
——26——CVE-2015-7569—86.7%
——26——CVE-2015-2092—86.7%
——26——CVE-2007-4901—86.7%
——26——CVE-2020-24386—86.7%
——26——CVE-2015-5794—86.7%
——26——CVE-2015-3240—86.7%
——26——CVE-2015-7048—86.7%
——26——CVE-2019-0805—86.7%
——26——CVE-2021-22767—86.7%
——26——CVE-2014-9234—86.7%
——26——CVE-2013-5917—86.7%
——26——CVE-2022-43019—86.7%
——26——CVE-2021-21876—86.7%
——26——CVE-2018-11357—86.7%
——26——CVE-2002-1007—86.7%
——26——CVE-2017-3862—86.7%
——26——