WSO2 Multiple Products: Exploited Flaw CVE-2026-5430
Published October 25, 2026 · Last updated October 25, 2026
What happened: On September 24, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-5430, a flaw in WSO2 Multiple Products, to its Known Exploited Vulnerabilities (KEV) catalog. The catalog lists flaws CISA has evidence attackers are using. CISA calls this one the "WSO2 Multiple Products Path Traversal Vulnerability ."
CISA's summary: "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. "
What the National Vulnerability Database says
NVD first published CVE-2026-5430 on August 6, 2026. Its description, from the record's source (ed10eef1-636d-4fbe-9993-6890dfa878f8), reads: "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."
How serious is CVE-2026-5430?
The CVSS 3.1 base score is 10.0 out of 10 (Critical), scored by ed10eef1-636d-4fbe-9993-6890dfa878f8. In plain terms: an attacker can reach the Multiple Products weakness over a network, including the internet; the attacker does not need an account; no one has to click or open anything. The listed impact on Multiple Products data secrecy is high, on data integrity high, and on availability high. The full vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.
Which Multiple Products versions are affected?
The CVE record lists these affected ranges:
- 4.5.0 up to, but not including, 4.5.0.57
- 4.6.0 up to, but not including, 4.6.0.21
- 4.5.0 up to, but not including, 4.5.0.56
- 4.6.0 up to, but not including, 4.6.0.21
- 4.5.0 up to, but not including, 4.5.0.58
- 4.6.0 up to, but not including, 4.6.0.22
- 4.1.0 up to, but not including, 4.1.0.257
- 4.2.0 up to, but not including, 4.2.0.197
If your Multiple Products version falls in one of these ranges, check WSO2's advisory for the fixed release that applies to you.
What kind of weakness is it?
CISA and NVD map CVE-2026-5430 to the following weakness type in MITRE's Common Weakness Enumeration (CWE):
- CWE-347: Improper Verification of Cryptographic Signature. MITRE's definition: "The product does not verify, or incorrectly verifies, the cryptographic signature for data."
CISA required action for CVE-2026-5430
CISA's required action for this KEV catalog entry, quoted from the catalog record, is: "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."
Timeline for CVE-2026-5430
- August 6, 2026: NVD publishes CVE-2026-5430.
- September 24, 2026: CISA adds CVE-2026-5430 to the KEV catalog.
- September 25, 2026: latest change to the NVD record (status: Analyzed).
- September 27, 2026: due date for U.S. federal civilian agencies to act on CVE-2026-5430.
Advisories and technical references
The NVD record for CVE-2026-5430 links to these references; tags in brackets are NVD's labels:
- security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026 (Vendor Advisory)
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-5430 (US Government Resource)
What to do
- Run WSO2 Multiple Products? Follow WSO2's own advisory (linked under Sources) and apply the fix or mitigation it lists. CISA's required action for this entry is to apply the vendor's mitigations, or stop using the product if no mitigation is available.
- Federal civilian agencies must act by September 27, 2026, CISA's due date for this entry. Other organizations can use that date as a deadline for Multiple Products too.
- Ransomware use: CISA lists known ransomware campaign use for CVE-2026-5430 as "Unknown".
- Don't run Multiple Products yourself? You don't need to install anything on your phone or home computer for this. If a call, text, or pop-up says your device is infected by "CVE-2026-5430" and asks for payment or remote access, that is a scam pattern, not a WSO2 alert.
CVE-2026-5430 record details from CISA and NVD
- CISA forensic triage flag for CVE-2026-5430: Yes
- Attack complexity for CVE-2026-5430: low
- CVE-2026-5430 CVSS scope: changed
- NVD sub-scores for CVE-2026-5430: exploitability 3.9, impact 6.0.
- Who mapped the weakness type: ed10eef1-636d-4fbe-9993-6890dfa878f8 (Secondary)
- NVD product identifiers (CPE):
cpe:2.3:a:wso2:api_control_plane:*:*:*:*:*:*:*:*,cpe:2.3:a:wso2:api_manager:*:*:*:*:*:*:*:*,cpe:2.3:a:wso2:traffic_manager:*:*:*:*:*:*:*:*,cpe:2.3:a:wso2:universal_gateway:*:*:*:*:*:*:*:* - References in the NVD record: 2 (1 tagged Vendor Advisory, 1 tagged US Government Resource).
- CISA SSVC decision points for CVE-2026-5430 (from NVD): exploitation=active; automatable=yes; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).
Sources
General education only, not security advice. Facts checked against the sources above on the date shown.