CVE-2026-5430: WSO2 Multiple Products Path Traversal Vulnerability

In short

WSO2 Multiple Products has a weakness classified as improper verification of cryptographic signature (CWE-347). CISA added it to its Known Exploited Vulnerabilities catalog on 2026-09-24. NVD lists CVSS 3.1 at 10 CRITICAL.

What it is

“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.” — CISA KEV, retrieved 2026-11-01

“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.” — NVD, retrieved 2026-11-01

Who is affected

WSO2 Multiple Products. NVD lists the following versions as affected:

• wso2 API Control Plane: from 4.5.0 inclusive, before 4.5.0.58
• wso2 API Control Plane: from 4.6.0 inclusive, before 4.6.0.22
• wso2 API Manager: from 4.1.0 inclusive, before 4.1.0.257
• wso2 API Manager: from 4.2.0 inclusive, before 4.2.0.197
• wso2 API Manager: from 4.3.0 inclusive, before 4.3.0.108
• wso2 API Manager: from 4.4.0 inclusive, before 4.4.0.72
• wso2 API Manager: from 4.5.0 inclusive, before 4.5.0.57
• wso2 API Manager: from 4.6.0 inclusive, before 4.6.0.21
• wso2 Traffic Manager: from 4.5.0 inclusive, before 4.5.0.56
• wso2 Traffic Manager: from 4.6.0 inclusive, before 4.6.0.21
• wso2 Universal Gateway: from 4.5.0 inclusive, before 4.5.0.57
• wso2 Universal Gateway: from 4.6.0 inclusive, before 4.6.0.21

Exploitation status

CISA KEV added: 2026-09-24. Known ransomware campaign use: Not reported by CISA. Due date CISA set for US federal civilian agencies: 2026-09-27.

Scores

NVD CVSS 3.1: 10 CRITICAL; vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H; source ed10eef1-636d-4fbe-9993-6890dfa878f8.

EPSS by FIRST: 22.39%; percentile 97.69; score date 2026-10-31. EPSS estimates the probability of exploitation in the next 30 days.

CWE: CWE-347.

Timeline

CISA 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.” — CISA KEV

What to do

• Confirm whether you run WSO2 Multiple Products and which version.
• Apply the vendor update or mitigation in the advisory.
• Follow CISA’s required action.
• Review the vendor guidance on signs of compromise.
• Track the fix through completion.

References

• Vendor Advisory: https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5328/
• NVD detail
• CVE.org record
• CISA KEV catalog

Sources and dates

CISA Known Exploited Vulnerabilities Catalog, version 2026.10.30; retrieved 2026-11-01. CISA KEV data: CC0 1.0. No endorsement by CISA.

NVD retrieved: 2026-11-01. This product uses the NVD API but is not endorsed or certified by the NVD.

EPSS scores by FIRST; score date 2026-10-31.