Skip to content
Server Security Center
KEVcritical10.0

CVE-2026-5430: WSO2 Multiple Products Path Traversal

WSO2 Multiple Products · listed in the CISA catalog of actively exploited vulnerabilities since 2026-09-24.

CVSS v3.1 (CVE record)
10.0
critical
EPSS (exploit probability, 30 days)
79%
higher than 99.6% of all CVEs
Added to CISA KEV
2026-09-24
US federal due date 2026-09-27
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2026-5430 explained

CVE-2026-5430 is a critical flaw in the JWT authentication of several WSO2 server products, including WSO2 API Manager. The mechanism accepts tokens signed with algorithms that are not configured or supported, so forged tokens can pass validation. CISA lists it as known exploited, and it can lead to administrative account takeover.

Impact

A remote attacker needs no credentials and no user interaction. By presenting a JWT signed with an unsupported algorithm, the attacker can gain unauthorized access, including administrative accounts and full account takeover. Confidentiality, integrity and availability impacts are all high. CISA rates it automatable with total technical impact, so it can be exploited at scale. The CNA notes the score is 9.8 in single-tenant deployments, where impact stays within one security authority boundary.

Who is affected

WSO2 API Manager is affected in the 4.1.0, 4.2.0, 4.3.0, 4.4.0, 4.5.0 and 4.6.0 lines. Fixes are in 4.1.0.257, 4.2.0.197, 4.3.0.108, 4.4.0.72, 4.5.0.57 and 4.6.0.21. WSO2 Universal Gateway is fixed in 4.5.0.57 and 4.6.0.21. WSO2 Traffic Manager is fixed in 4.5.0.56 and 4.6.0.21. WSO2 API Control Plane is fixed in 4.5.0.58 and 4.6.0.22. WSO2 Carbon API Manager Rest API Utility is fixed in 9.20.74.401, 9.28.116.417, 9.29.120.236, 9.30.67.167, 9.31.86.158 and 9.32.147.59.

Written with AI from the data on this page and checked against it automatically.

Official 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.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • WSO2 Universal Gateway
    Affected
    • ≥ 4.5.0, < 4.5.0.57
    • ≥ 4.6.0, < 4.6.0.21
    Fixed in
    • 4.5.0.57
    • 4.6.0.21
  • WSO2 Traffic Manager
    Affected
    • ≥ 4.5.0, < 4.5.0.56
    • ≥ 4.6.0, < 4.6.0.21
    Fixed in
    • 4.5.0.56
    • 4.6.0.21
  • WSO2 API Control Plane
    Affected
    • ≥ 4.5.0, < 4.5.0.58
    • ≥ 4.6.0, < 4.6.0.22
    Fixed in
    • 4.5.0.58
    • 4.6.0.22
  • WSO2 API Manager
    Affected
    • ≥ 4.1.0, < 4.1.0.257
    • ≥ 4.2.0, < 4.2.0.197
    • ≥ 4.3.0, < 4.3.0.108
    • ≥ 4.4.0, < 4.4.0.72
    • ≥ 4.5.0, < 4.5.0.57
    • ≥ 4.6.0, < 4.6.0.21
    Fixed in
    • 4.1.0.257
    • 4.2.0.197
    • 4.3.0.108
    • 4.4.0.72
    • 4.5.0.57
    • 4.6.0.21
  • WSO2 Carbon API Manager Rest API Utility
    Affected
    • ≥ 9.20.74, < 9.20.74.401
    • ≥ 9.28.116, < 9.28.116.417
    • ≥ 9.29.120, < 9.29.120.236
    • ≥ 9.30.67, < 9.30.67.167
    • ≥ 9.31.86, < 9.31.86.158
    • ≥ 9.32.147, < 9.32.147.59
    Fixed in
    • 9.20.74.401
    • 9.28.116.417
    • 9.29.120.236
    • 9.30.67.167
    • 9.31.86.158
    • 9.32.147.59

How to fix it

  • Update to the fixed version for your product:
    • WSO2 Universal Gateway: 4.5.0.57, 4.6.0.21
    • WSO2 Traffic Manager: 4.5.0.56, 4.6.0.21
    • WSO2 API Control Plane: 4.5.0.58, 4.6.0.22
    • WSO2 API Manager: 4.1.0.257, 4.2.0.197, 4.3.0.108, 4.4.0.72, 4.5.0.57, 4.6.0.21
    • WSO2 Carbon API Manager Rest API Utility: 9.20.74.401, 9.28.116.417, 9.29.120.236, 9.30.67.167, 9.31.86.158, 9.32.147.59
  • Vendor advisory: security.docs.wso2.com/en/latest/security-announcements/s…
  • CISA's deadline for US federal agencies: 2026-09-27 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Identify every WSO2 Universal Gateway, Traffic Manager, API Control Plane, API Manager and Carbon API Manager Rest API Utility instance and its version.
  2. Update each instance to the fixed version for its release line as listed in the CVE record.
  3. Apply any mitigations in the WSO2 advisory where updating cannot happen immediately, per CISA's required action.
  4. Restrict network access to WSO2 management and API endpoints, and keep administrative interfaces off the internet.
  5. Check for signs of compromise, such as unexpected administrative logins or account changes, following CISA's forensics triage guidance.
  6. If neither a fix nor mitigations can be applied, follow CISA's guidance to discontinue use of the product.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-347 Improper Validation of Certificate With Host Mismatch

Questions about CVE-2026-5430

Is this vulnerability being exploited?
Yes. CISA added CVE-2026-5430 to its Known Exploited Vulnerabilities catalog on 2026-09-24, with a US federal due date of 2026-09-27. Whether it is used in ransomware campaigns is unknown.
Do attackers need an account to exploit it?
No. It is exploitable over the network with low complexity, no privileges and no user interaction. CISA also rates it automatable, meaning it can be exploited at scale.
Why is the score different for single-tenant deployments?
The CNA lists a base score of 10.0 with changed scope. In single-tenant deployments it adjusts the score to 9.8, because the impact stays within a single security authority boundary. Both cases are critical and should be patched.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.