cve.bz

CVE-2026-5430 WSO2 Multiple Products Path Traversal Vulnerability

10.0 criticalKEVEPSS 79%Fix available

Critical (10.0) in WSO2 Multiple Products. In CISA KEV since 2026-09-24. EPSS 79% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

10.0 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
79% (up from 22% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-09-24, due 2026-09-27
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2026-09-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-5430 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-5430?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-5430?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-5430 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
WSO2 Universal Gatewayfrom 4.5.0 before 4.5.0.57
WSO2 Universal Gatewayfrom 4.6.0 before 4.6.0.21
WSO2 Traffic Managerfrom 4.5.0 before 4.5.0.56
WSO2 Traffic Managerfrom 4.6.0 before 4.6.0.21
WSO2 API Control Planefrom 4.5.0 before 4.5.0.58
WSO2 API Control Planefrom 4.6.0 before 4.6.0.22
WSO2 API Managerfrom 4.1.0 before 4.1.0.257
WSO2 API Managerfrom 4.2.0 before 4.2.0.197
WSO2 API Managerfrom 4.3.0 before 4.3.0.108
WSO2 API Managerfrom 4.4.0 before 4.4.0.72
WSO2 API Managerfrom 4.5.0 before 4.5.0.57
WSO2 API Managerfrom 4.6.0 before 4.6.0.21
WSO2 Carbon API Manager Rest API Utilityfrom 9.20.74 before 9.20.74.401
WSO2 Carbon API Manager Rest API Utilityfrom 9.28.116 before 9.28.116.417
WSO2 Carbon API Manager Rest API Utilityfrom 9.29.120 before 9.29.120.236
WSO2 Carbon API Manager Rest API Utilityfrom 9.30.67 before 9.30.67.167
WSO2 Carbon API Manager Rest API Utilityfrom 9.31.86 before 9.31.86.158
WSO2 Carbon API Manager Rest API Utilityfrom 9.32.147 before 9.32.147.59

Fixed in

ProductFixed in
WSO2 Carbon API Manager Rest API Utility9.33.106

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • abraxas/CVE-2026-5430 Harbor Check: matches CVE 2 stars, Python, created
    CVE-2026-5430 - WSO2 API Manager - Critical 10.0 - Unauthenticated Account Takeover - WSO2 API Control Plane, WSO2 API Manager, WSO2 Traffi…
  • davidvrns/CVE-2026-5430-WSO2 Harbor Check: matches CVE 1 star, Python, created
    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 assess…
  • getdrive/wso2_cve-2026-5430_lab Harbor Check: matches CVE 0 stars, Python, created
    Уязвимая лаборатория WSO2 API Manager 4.5.0 в Docker, сканер и эксплойт для CVE-2026-5430 (обход аутентификации через поддельный HS256 JWT)
  • HORKimhab/CVE-2026-5430 0 stars, created
    CVE-2026-5430 - Draft or TODO

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON