CVE-2026-5430 — WSO2 Multiple Products Path Traversal Vulnerability
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (github)+6
- EPSS 0.6% (30-day exploitation probability)+7
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
CISA required action CISA
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.
US federal deadline: Sep 27, 2026 — passed 18 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (WSO2 Api Control Plane, WSO2 Api Manager, WSO2 Traffic Manager…).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (cryptography), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| WSO2 | Api Control Plane | ≥ 4.6.0 and < 4.6.0.22≥ 4.5.0 and < 4.5.0.58 | Vulnerable | NIST National Vulnerability Database |
| WSO2 | Api Control Plane | ≥ 4.5.0 and < 4.5.0.58≥ 4.6.0 and < 4.6.0.22 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | Api Manager | ≥ 4.6.0 and < 4.6.0.21≥ 4.5.0 and < 4.5.0.57≥ 4.4.0 and < 4.4.0.72≥ 4.3.0 and < 4.3.0.108≥ 4.2.0 and < 4.2.0.197≥ 4.1.0 and < 4.1.0.257 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | Api Manager | ≥ 4.5.0 and < 4.5.0.57≥ 4.4.0 and < 4.4.0.72≥ 4.3.0 and < 4.3.0.108≥ 4.2.0 and < 4.2.0.197≥ 4.1.0 and < 4.1.0.257≥ 4.6.0 and < 4.6.0.21 | Vulnerable | NIST National Vulnerability Database |
| WSO2 | Traffic Manager | ≥ 4.5.0 and < 4.5.0.56≥ 4.6.0 and < 4.6.0.21 | Vulnerable | NIST National Vulnerability Database |
| WSO2 | Traffic Manager | ≥ 4.5.0 and < 4.5.0.56≥ 4.6.0 and < 4.6.0.21 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | Universal Gateway | ≥ 4.5.0 and < 4.5.0.57≥ 4.6.0 and < 4.6.0.21 | Vulnerable | NIST National Vulnerability Database |
| WSO2 | Universal Gateway | ≥ 4.6.0 and < 4.6.0.21≥ 4.5.0 and < 4.5.0.57 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | WSO2 Carbon API Manager Rest API Utility | ≥ 9.20.74 and < 9.20.74.401≥ 9.28.116 and < 9.28.116.417≥ 9.29.120 and < 9.29.120.236≥ 9.30.67 and < 9.30.67.167≥ 9.31.86 and < 9.31.86.158≥ 9.32.147 and < 9.32.147.59 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 10.0 | CVSS 3.1 | Critical | 3.9 | 6.0 | ed10eef1-636d-4fbe-9993-6890dfa878f8 via NIST National Vulnerability Database |
| 10.0 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 10.0 | CVSS 3.1 | Critical | — | — | WSO2 via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (score shown at the top: ed10eef1-636d-4fbe-9993-6890dfa878f8) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- 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 ★ 1 Sep 25, 2026
- CVE-2026-5430 - Draft or TODO ★ 0 Sep 16, 2026
- 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. ★ 0 Oct 8, 2026
- Уязвимая лаборатория WSO2 API Manager 4.5.0 в Docker, сканер и эксплойт для CVE-2026-5430 (обход аутентификации через поддельный HS256 JWT) ★ 0 Oct 8, 2026
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.59%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Check TLS negotiations and unexpected certificates in the component’s traffic.
- Hunt retroactively in logs from before Sep 24, 2026 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · wso2/wso2 universal gateway, wso2/wso2 traffic manager, wso2/wso2 api control plane, wso2/wso2 api manager, wso2/wso2 ca
- SSVC assessment updated
- Record published
- Affected products added · wso2/api control plane, wso2/api manager, wso2/traffic manager, wso2/universal gateway
- CVSS changed · 10.0
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- Added to CISA KEV catalog
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
5 on the record
- security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5
- github.com/advisories/GHSA-j7vh-5w8q-4m4x
- nvd.nist.gov/vuln/detail/CVE-2026-5430
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-1728 Improper Privilege Management in WSO2 Api Control Plane Aug 6, 2026
- Medium CVE-2026-0637 Insertion of Sensitive Information into Log File in WSO2 Api Control Plane Aug 6, 2026
- Critical CVE-2025-15039 The Conditional Authentication (Adaptive Authentication) script does not correctly… Aug 6, 2026
- Low CVE-2025-13736 Observable Discrepancy in WSO2 Api Manager Aug 6, 2026
- Medium CVE-2025-13394 Cross-Site Request Forgery (CSRF) in WSO2 Api Control Plane Aug 6, 2026
- Medium CVE-2024-8995 Unused authorization codes issued to deleted users are not being properly invalidated or… Aug 6, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-5430 is "WSO2 Multiple Products Path Traversal Vulnerability", rated Critical. It affects Api Control Plane (WSO2); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 10.0 describes technical severity. EPSS 0.59% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.