CVE-2026-5430

Critical

WSO2 Multiple Products Path Traversal Vulnerability

10.0 CVSS v3.1

Published: Aug 6, 2026
Updated: Sep 25, 2026
Vendor: Wso2
Affected versions: See affected products
Weakness: CWE-347

Summary

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.

Severity

Critical (10.0)

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected products

Wso2 Api Control Plane >= 4.5.0, < 4.5.0.58
Wso2 Api Control Plane >= 4.6.0, < 4.6.0.22
Wso2 Api Manager >= 4.1.0, < 4.1.0.257
Wso2 Api Manager >= 4.2.0, < 4.2.0.197
Wso2 Api Manager >= 4.3.0, < 4.3.0.108
Wso2 Api Manager >= 4.4.0, < 4.4.0.72
Wso2 Api Manager >= 4.5.0, < 4.5.0.57
Wso2 Api Manager >= 4.6.0, < 4.6.0.21
Wso2 Traffic Manager >= 4.5.0, < 4.5.0.56
Wso2 Traffic Manager >= 4.6.0, < 4.6.0.21
Wso2 Universal Gateway >= 4.5.0, < 4.5.0.57
Wso2 Universal Gateway >= 4.6.0, < 4.6.0.21

Exploitation status

Actively exploited

Listed in the CISA Known Exploited Vulnerabilities catalog on Sep 24, 2026. Federal remediation due: Sep 27, 2026.

Technical details

Technical analysis has not been written for this record yet.

Mitigation & remediation

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.