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

> Attackers can bypass authentication by crafting JWTs with unsupported algorithms, leading to unauthorized access and potential administrative account takeover in WSO2 products.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 24 Sep 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-j7vh-5w8q-4m4x

## What is CVE-2026-5430?

CVE-2026-5430 is a critical authentication bypass vulnerability in Wso2 Api Manager, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-5430?

It affects 4 products.


Products: Wso2 Api Control Plane, Wso2 Api Manager, Wso2 Traffic Manager, Wso2 Universal Gateway.

## How do I fix CVE-2026-5430?

No fix has been published for CVE-2026-5430 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 27 Sep 2026.

## Is CVE-2026-5430 being exploited?

Yes. Attackers have exploited CVE-2026-5430 in the wild since at least 24 Sep 2026.

Public exploit code:

- CVE-2026-5430 - WSO2 API Manager - Critical 10.0 - Unauthenticated Account Takeover - WSO2 API Control Plane, WSO2 API Manager, WSO2 Traffic Manager, WSO2 Universal Gateway (github_poc): https://github.com/abraxas/CVE-2026-5430
- Detection PoC for CVE-2026-5430 — unauthenticated JWT algorithm bypass (CVSS 10.0) affecting WSO2 API Manager 4.1.0–4.6.0. Read-only assessment tool with patch confirmation and WAF detection. Authorized use only. (github_poc): https://github.com/davidvrns/CVE-2026-5430-WSO2
- CVE-2026-5430 - Draft or TODO (github_poc): https://github.com/HORKimhab/CVE-2026-5430
- Уязвимая лаборатория WSO2 API Manager 4.5.0 в Docker, сканер и эксплойт для CVE-2026-5430 (обход аутентификации через поддельный HS256 JWT) (github_poc): https://github.com/getdrive/wso2_cve-2026-5430_lab

## Other vulnerabilities in Wso2 Api Manager

- [CVE-2026-1728](https://insights.sbomify.com/CVE-2026-1728/): Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover (critical 9.8)
- [CVE-2025-9312](https://insights.sbomify.com/CVE-2025-9312/): Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products (critical 9.8)
- [CVE-2025-10611](https://insights.sbomify.com/CVE-2025-10611/): Potential Broken Access Control in Multiple WSO2 Products via System REST APIs (critical 9.8)
- [CVE-2025-9152](https://insights.sbomify.com/CVE-2025-9152/): Improper Privilege Management in Multiple WSO2 API Manager via keymanager-operations DCR Endpoint (critical 9.8)
- [CVE-2025-9804](https://insights.sbomify.com/CVE-2025-9804/): Improper Access Control in Multiple WSO2 Products via Internal SOAP Admin Services and System REST APIs (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5430 and fix it if it is affected.

What it is: CVE-2026-5430 is a critical authentication bypass vulnerability in Wso2 Api Manager, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-5430 in the wild since at least 24 Sep 2026.

Affected product: Wso2 Api Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5430/ (Markdown: https://insights.sbomify.com/CVE-2026-5430/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5430
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5430
- OSV: https://osv.dev/vulnerability/CVE-2026-5430

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5430/
Summaries are generated and may contain mistakes; the official description above is the record.