Vulnerabilidades exploráveis hoje
413,805na 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,615
- Alta22,524
- Média20,884
- Baixa2,135
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2019-7822—95.5%
——29——CVE-2020-8868—95.5%
——29——CVE-2006-1728—95.5%
——29——CVE-2021-253297.0 ALT95.5%
——29The fix for CVE-2020-9484 was incomplete. When using Apache Tomcat 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41, 8.5.0 to 8.5.61 or 7.0.0. to 7.0.107 with a configuration edge case that was highly unlikely to be used, the Tomcat instance was still vulnerable to CVE-2020-9494. Note that both the previously published prerequisites for CVE-2020-9484 and the previously published mitigations for CVE-2020-9484 also apply to this issue.35dCVE-2022-32275—95.5%
——29——CVE-2013-2576—95.5%
——29——CVE-2018-12784—95.5%
——29——CVE-2008-3996—95.5%
——29——CVE-2015-6490—95.5%
——29——CVE-2002-1178—95.5%
——29——CVE-2010-1722—95.5%
——29——CVE-2002-0068—95.5%
——29——CVE-2000-0202—95.5%
——29——CVE-2013-1299—95.5%
——29——CVE-1999-0926—95.5%
——29——CVE-2020-16199—95.5%
——29——CVE-2009-3874—95.5%
——29——CVE-2006-6740—95.5%
——29——CVE-2019-0802—95.5%
——29——CVE-2009-2109—95.5%
——29——CVE-2011-0742—95.5%
——29——CVE-2020-25858—95.5%
——29——CVE-2011-1470—95.5%
——29——CVE-2017-14064—95.5%
——29——CVE-2015-2544—95.5%
——29——CVE-2024-300877.8 ALT95.5%
——29Win32k Elevation of Privilege Vulnerability115dCVE-2017-3059—95.5%
——29——CVE-2007-4504—95.5%
——29——CVE-2015-7259—95.5%
——29——CVE-2015-2543—95.5%
——29——CVE-2018-18793—95.5%
——29——CVE-2013-5948—95.5%
——29——CVE-2010-1474—95.5%
——29——CVE-2019-7800—95.5%
——29——CVE-2025-599349.4 CRÍ95.5%
——29Formbricks is an open source qualtrics alternative. Prior to version 4.0.1, Formbricks is missing JWT signature verification. This vulnerability stems from a token validation routine that only decodes JWTs (jwt.decode) without verifying their signatures. Both the email verification token login path and the password reset server action use the same validator, which does not check the token’s signature, expiration, issuer, or audience. If an attacker learns the victim’s actual user.id, they can craft an arbitrary JWT with an alg: "none" header and use it to authenticate and reset the victim’s password. This issue has been patched in version 4.0.1.24dCVE-2007-2390—95.5%
——29——CVE-2005-0838—95.5%
——29——CVE-2017-9789—95.5%
——29——CVE-2007-2677—95.5%
——29——CVE-2014-9374—95.5%
——29——