Skip to content
CVSS 10.0CVSS 10.0 · CRITICAL

CVE-2026-5430Authentication bypass in JWT token validation

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.

View on NVD

Analysis

Esta vulnerabilidad en el mecanismo de autenticación JWT permite a un atacante falsificar tokens utilizando algoritmos de firma no configurados para saltarse la validación. El impacto directo es el acceso no autorizado y la toma de control total de cuentas, incluyendo perfiles administrativos. Es un riesgo crítico para cualquier aplicación que dependa de JWT para la gestión de identidad y sesiones.

Relevant roles

BackendFrontendJavascriptTypescriptCyberSecurityJava

Severity

Score: 10.0(CRITICAL)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
AV: NETWORK
AC: LOW
PR: NONE
UI: NONE
S: CHANGED
C: HIGH
I: HIGH
A: HIGH
Weakness (CWE): CWE-347

EPSS

Probability of exploitation (next 30 days): 0.0022 (0.2%)
Percentile: 12.9%
EPSS: 2026-08-06

Technical description

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.

Published: 8/6/2026, 8:16:33 AM
Last modified: 8/6/2026, 3:31:57 PM

References

HomeEventsBlogResourcesCoursesTeam