WaratekVRT Sign in
Reset
More filters (1)
Columns
CWE CWE-347✕
Overview 4 matches · 0 protected · 1 exploited · 1 CISA KEV · 3 public PoC · 0 EPSS ≥ 0.5
4matches 0protected0.0% 1exploited25.0% 1CISA KEV25.0% 3public PoC75.0% 0EPSS ≥ 0.50.0%
Protected by Waratek 0 0.0% Rule in development 0 0.0% Mitigation candidate 4 100.0% No exploit published 0 0.0%
Critical 2 50.0% High 2 50.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 0 0.0% partly blocked 0 0.0% not blocked 3 75.0% not established 1 25.0% unrecorded 0 0.0%
Exploited 1 25.0% Working exploit published 1 25.0% Proof of concept only 2 50.0% Forecast only 0 0.0% No public exploit 0 0.0%
split by peak 2 / quarter
Mitigation candidate: 4 High: 2Critical: 2 not established: 1not blocked: 3 Proof of concept only: 2Working exploit published: 1Exploited: 1
Q3 241 Mitigation candidate1 High1 not blocked1 Working exploit published1 Q4 240 Q1 250 Q2 250 Q3 250 Q4 250 Q1 262 Mitigation candidate2 Critical1 High1 not blocked2 Proof of concept only2 Q2 260 Q3 261 Mitigation candidate1 Critical1 not established1 Exploited1
Q3 24Q4 24Q1 25Q2 25Q3 25Q4 25Q1 26Q2 26Q3 26
4 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2026-5430 Critical 2026-08-06 Mitigation candidate Exploited The JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or supported. This allows an attacker to craft a JWT with an unsupported algorithm, which is then incorrectly validated, leading to unauthorized access. Successful exploitation of this vulnerability may result in unauthorized access to the system, including the potential compromise of administrative accounts and full account takeover. The CVSS score is adjusted to 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) in single-tenant deployments, reflecting that the impact is contained within a single security authority boundary.
CVE-2026-29000 Critical 2026-03-04 Mitigation candidate Proof of concept only pac4j-jwt versions prior to 4.5.9, 5.7.9, and 6.3.3 contain an authentication bypass vulnerability in JwtAuthenticator when processing encrypted JWTs that allows remote attackers to forge authentication tokens. Attackers who possess the server's RSA public key can create a JWE-wrapped PlainJWT with arbitrary subject and role claims, bypassing signature verification to authenticate as any user including administrators.
CVE-2026-1529 High 2026-02-09 Mitigation candidate Proof of concept only A flaw was found in Keycloak. An attacker can exploit this vulnerability by modifying the organization ID and target email within a legitimate invitation token's JSON Web Token (JWT) payload. This lack of cryptographic signature verification allows the attacker to successfully self-register into an unauthorized organization, leading to unauthorized access.
CVE-2024-8698 High 2024-09-19 Mitigation candidate Working exploit published A flaw exists in the SAML signature validation method within the Keycloak XMLSignatureUtil class. The method incorrectly determines whether a SAML signature is for the full document or only for specific assertions based on the position of the signature in the XML document, rather than the Reference element used to specify the signed element. This flaw allows attackers to create crafted responses that can bypass the validation, potentially leading to privilege escalation or impersonation attacks.