CyberSecBulletin
CVE-2026-5430Exploited in the wildNVD status: Analyzed

WSO2 Multiple Products Path Traversal

Published Updated By the CyberSecBulletin desk

CVE-2026-5430 is a critical-severity improper verification of cryptographic signature vulnerability in WSO2 Universal Gateway from WSO2, with a CVSS 3.1 base score of 10.0 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 4.5.0.57, 4.6.0.21 as the first without the flaw, so updating WSO2 Universal Gateway to one of those releases or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on September 24, 2026, which means attacks have been observed in the wild.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Update WSO2 Universal Gateway to 4.5.0.57 or 4.6.0.21, whichever matches your release line, or a later version.
  2. Update WSO2 Traffic Manager to 4.5.0.56 or 4.6.0.21, whichever matches your release line, or a later version.
  3. Update WSO2 API Control Plane to 4.5.0.58 or 4.6.0.22, whichever matches your release line, or a later version.
  4. CISA's required action: 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.
  5. Read the advisory on security.docs.wso2.com for workarounds and exact fixed builds.
  6. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
WSO2WSO2 Universal Gateway4.5.0 up to, but not including, 4.5.0.57; 4.6.0 up to, but not including, 4.6.0.214.5.0.57, 4.6.0.21
WSO2WSO2 Traffic Manager4.5.0 up to, but not including, 4.5.0.56; 4.6.0 up to, but not including, 4.6.0.214.5.0.56, 4.6.0.21
WSO2WSO2 API Control Plane4.5.0 up to, but not including, 4.5.0.58; 4.6.0 up to, but not including, 4.6.0.224.5.0.58, 4.6.0.22
WSO2WSO2 API Manager4.1.0 up to, but not including, 4.1.0.257; 4.2.0 up to, but not including, 4.2.0.197; 4.3.0 up to, but not including, 4.3.0.108; 4.4.0 up to, but not including, 4.4.0.72; 4.5.0 up to, but not including, 4.5.0.57; 4.6.0 up to, but not including, 4.6.0.214.1.0.257, 4.2.0.197, 4.3.0.108, 4.4.0.72, 4.5.0.57, 4.6.0.21
WSO2WSO2 Carbon API Manager Rest API Utility9.20.74 up to, but not including, 9.20.74.401; 9.28.116 up to, but not including, 9.28.116.417; 9.29.120 up to, but not including, 9.29.120.236; 9.30.67 up to, but not including, 9.30.67.167; 9.31.86 up to, but not including, 9.31.86.158; 9.32.147 up to, but not including, 9.32.147.599.20.74.401, 9.28.116.417, 9.29.120.236, 9.30.67.167, 9.31.86.158, 9.32.147.59
WSO2API Control Plane4.5.0 up to, but not including, 4.5.0.58; 4.6.0 up to, but not including, 4.6.0.224.5.0.58, 4.6.0.22
WSO2API Manager4.1.0 up to, but not including, 4.1.0.257; 4.2.0 up to, but not including, 4.2.0.197; 4.3.0 up to, but not including, 4.3.0.108; 4.4.0 up to, but not including, 4.4.0.72; 4.5.0 up to, but not including, 4.5.0.57; 4.6.0 up to, but not including, 4.6.0.214.1.0.257, 4.2.0.197, 4.3.0.108, 4.4.0.72, 4.5.0.57, 4.6.0.21
WSO2Traffic Manager4.5.0 up to, but not including, 4.5.0.56; 4.6.0 up to, but not including, 4.6.0.214.5.0.56, 4.6.0.21
WSO2Universal Gateway4.5.0 up to, but not including, 4.5.0.57; 4.6.0 up to, but not including, 4.6.0.214.5.0.57, 4.6.0.21

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. Scored by CNA.

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Verification of Cryptographic Signature

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

More Improper Verification of Cryptographic Signature vulnerabilities (CWE-347)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: active, automatable: yes, technical impact: total).
  3. Added to CISA's Known Exploited Vulnerabilities catalogue.
  4. Record last changed materially (score, affected products, status or references).
  5. Deadline for US federal agencies to remediate, set by CISA.

References

Third-party and government advisories

Other vulnerabilities in WSO2 Universal Gateway

All WSO2 Universal Gateway vulnerabilities

Recent Improper Verification of Cryptographic Signature vulnerabilities

Spotted an error? Tell us.