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

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.

Exploitation evidence

First exploit evidence seen: 2026-09-16 (earliest date across the sources below).

Exploited in the wild

• CISA KEV: listed since 2026-09-24. Source

Public exploit code

GitHub proof-of-concept repositories

4 public repositories from 4 accounts, first seen 2026-09-16. Most starred: abraxas/CVE-2026-5430 (2 stars), view repository.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: CISA KEV · nomi-sec/PoC-in-GitHub.

How to fix it

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. (source: CISA KEV)

Fixed versions

• wso2 api control plane: upgrade to 4.5.0.58 or later (affected from 4.5.0)
• wso2 api control plane: upgrade to 4.6.0.22 or later (affected from 4.6.0)
• wso2 api manager: upgrade to 4.1.0.257 or later (affected from 4.1.0)
• wso2 api manager: upgrade to 4.2.0.197 or later (affected from 4.2.0)
• wso2 api manager: upgrade to 4.3.0.108 or later (affected from 4.3.0)
• wso2 api manager: upgrade to 4.4.0.72 or later (affected from 4.4.0)
• wso2 api manager: upgrade to 4.5.0.57 or later (affected from 4.5.0)
• wso2 api manager: upgrade to 4.6.0.21 or later (affected from 4.6.0)
• wso2 traffic manager: upgrade to 4.5.0.56 or later (affected from 4.5.0)
• wso2 traffic manager: upgrade to 4.6.0.21 or later (affected from 4.6.0)
• wso2 universal gateway: upgrade to 4.5.0.57 or later (affected from 4.5.0)
• wso2 universal gateway: upgrade to 4.6.0.21 or later (affected from 4.6.0)

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

• https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5328/ (CISA KEV notes)

MITRE ATT&CK mitigations for this chain

• M1038 Execution Prevention (for T1553) : System settings can prevent applications from running that haven't been downloaded through the Apple Store (or other legitimate repositories) which can help mitigate some of these issues. Also enable application control solutions such as AppLocker and/or Device Guard to block the loading of malicious content.
• M1028 Operating System Configuration (for T1553) : Windows Group Policy can be used to manage root certificates and the <code>Flags</code> value of <code>HKLM\\SOFTWARE\\Policies\\Microsoft\\SystemCertificates\\Root\\ProtectedRoots</code> can be set to 1 to prevent non-administrator users from making further root installations into their own HKCU certificate store.
• M1026 Privileged Account Management (for T1553) : Manage the creation, modification, use, and permissions associated to privileged accounts, including SYSTEM and root.
• M1024 Restrict Registry Permissions (for T1553) : Ensure proper permissions are set for Registry hives to prevent users from modifying keys related to SIP and trust provider components. Components may still be able to be hijacked to suitable functions already present on disk if malicious modifications to Registry keys are not prevented.
• M1054 Software Configuration (for T1553) : HTTP Public Key Pinning (HPKP) is one method to mitigate potential [Adversary-in-the-Middle](https://attack.mitre.org/techniques/T1557) situations where and adversary uses a mis-issued or fraudulent certificate to intercept encrypted communications by enforcing use of an expected certificate.

Detection Generic guidance

Response checklist Generic guidance

1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.