CVE-2026-5430 WSO2 Multiple Products Path Traversal Vulnerability
WSO2 API Control Plane, API Manager, Traffic Manager & Universal Gateway contain a path traversal vulnerability that could allow for unrestricted file upload and lead to remote code execution.
From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.
Should You Worry?
- CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 24 Sep 2026.
- Rated Critical severity (CVSS 10.0, scored by Vendor).
- It has been in the catalogue for 43 days. Systems still unpatched now have almost certainly been scanned for it.
What It Is
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.
Affected Versions
| Product | Versions |
|---|---|
| WSO2 WSO2 Universal Gateway | 4.5.0 to before 4.5.0.57 4.6.0 to before 4.6.0.21 |
| WSO2 WSO2 Traffic Manager | 4.5.0 to before 4.5.0.56 4.6.0 to before 4.6.0.21 |
| WSO2 WSO2 API Control Plane | 4.5.0 to before 4.5.0.58 4.6.0 to before 4.6.0.22 |
| WSO2 WSO2 API Manager | 4.1.0 to before 4.1.0.257 4.2.0 to before 4.2.0.197 4.3.0 to before 4.3.0.108 4.4.0 to before 4.4.0.72 4.5.0 to before 4.5.0.57 |
| WSO2 WSO2 Carbon API Manager Rest API Utility | 9.20.74 to before 9.20.74.401 9.28.116 to before 9.28.116.417 9.29.120 to before 9.29.120.236 9.30.67 to before 9.30.67.167 9.31.86 to before 9.31.86.158 9.32.147 to before 9.32.147.59 |
From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.
What To Do Now
- 1
Find it
Search your asset inventory and external attack surface for WSO2 Multiple Products. Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management - 2
Fix it
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.
Vulnerability Management - 3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response - 4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing
The Compliance Clock
General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.
Not Sure If You Are Exposed?
Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2026-5430 and every other exploited flaw on the list.