Skip to content
feed: live
>_0dayNews
wso2

WSO2 CVSS 10 JWT Bypass Exploited in the Wild

CVE-2026-5430 lets unauthenticated attackers forge JWTs and gain administrative access to WSO2 deployments. Active exploitation confirmed. Patch immediately.

WSO2 CVSS 10 JWT Bypass Exploited in the Wild
Image: 0dayNews / 0dayNews Editorial · All rights reserved
fuseMarisol "Fuse" Delgado·Published ·1 min read

Attackers are actively exploiting CVE-2026-5430, a CVSS 10.0 critical authentication bypass in WSO2 components. SecurityWeek reported enterprise warnings this week as exploitation was confirmed in production environments.

What the vulnerability does

WSO2’s JWT authentication mechanism fails to restrict the signing algorithms it will accept. An attacker can craft a JWT token using an algorithm outside of the configured or supported set. The implementation validates the token anyway, granting unauthorized access. No credentials, no privileges, no user interaction required.

The consequence: an unauthenticated attacker can obtain access to protected resources and, in many configurations, compromise administrative accounts. NVD’s CVE-2026-5430 record confirms the vulnerability was disclosed on August 6, 2026.

The CVSS base score is 10.0 in multi-tenant deployments. In single-tenant environments, the score adjusts to 9.8 because the impact is scoped to a single security boundary. Both scores are critical. The distinction matters for risk prioritization, not for whether to patch.

Who is at risk

Organizations running WSO2 products that use JWT validation for API access control or identity management. If your WSO2 deployment handles any external-facing authentication or API gateway functions, treat this as immediate priority. The use of JWT algorithm confusion attacks is not novel, but confirmed exploitation against a CVSS 10.0 flaw in widely deployed enterprise software demands fast response.

What to do

  1. Check WSO2’s security advisory portal for the patch specific to your product version and apply it immediately.
  2. Until patched, restrict network access to WSO2 administrative interfaces.
  3. Pull your access logs and review JWT requests for tokens using unexpected algorithm types. Tokens signed with “none,” HMAC algorithms when RSA is expected, or any algorithm outside your configured set are indicators of abuse.

The September Pixel modem zero-day and Cisco ISE CVSS 10.0 auth bypass patched this week underline that this is not a light patch cycle. WSO2 CVE-2026-5430 belongs in the same bucket: fix it before the weekend.

Found this useful? Share it.