CVE-2026-5430: Authentication Bypass via JWT Algorithm Mismatch in Multiple WSO2 Products Allows Account Takeover
Noroxi assessment
Priority: This week (action score 77/100)
- CISA has confirmed exploitation in the wild (Sep 24, 2026). Remediation deadline for US federal agencies: Sep 27, 2026.
- Probability of exploitation in the next 30 days: 22.3% (FIRST EPSS); higher than 97.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Don’t wait for the next maintenance window. Until a fix is released, restrict access to the affected component and follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS
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.
- Published
- Aug 6, 2026
- Updated
- Sep 25, 2026
- EPSS
- 22.3% · 97th percentile
- CWE
- CWE-347
Report tools
Action score
77
This week
Don’t wait for the next maintenance window.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 7 / 30 · 22.3%
CISA SSVC decision
- Exploitation
- active
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · WSO2
- 10.0
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Sep 24, 2026. That signals real attacks, not theory.
Remediation deadline for US federal agencies: Sep 27, 2026.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| wso2 | api control plane | cpe:2.3:a:wso2:api_control_plane |
| wso2 | api manager | cpe:2.3:a:wso2:api_manager |
| wso2 | traffic manager | cpe:2.3:a:wso2:traffic_manager |
| wso2 | universal gateway | cpe:2.3:a:wso2:universal_gateway |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wso2 api control plane4.5.0 and later · before 4.5.0.58
- wso2 api control plane4.6.0 and later · before 4.6.0.22
- wso2 api manager4.1.0 and later · before 4.1.0.257
- wso2 api manager4.2.0 and later · before 4.2.0.197
- wso2 api manager4.3.0 and later · before 4.3.0.108
- wso2 api manager4.4.0 and later · before 4.4.0.72
- wso2 api manager4.5.0 and later · before 4.5.0.57
- wso2 api manager4.6.0 and later · before 4.6.0.21
- wso2 traffic manager4.5.0 and later · before 4.5.0.56
- wso2 traffic manager4.6.0 and later · before 4.6.0.21
- wso2 universal gateway4.5.0 and later · before 4.5.0.57
- wso2 universal gateway4.6.0 and later · before 4.6.0.21
Versions reported by the vendor
Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.
WSO2 WSO2 API Control Plane
- 4.5.0 and later · before 4.5.0.58affected
- 4.6.0 and later · before 4.6.0.22affected
WSO2 WSO2 API Manager
- before 4.1.0unknown
- 4.1.0 and later · before 4.1.0.257affected
- 4.2.0 and later · before 4.2.0.197affected
- 4.3.0 and later · before 4.3.0.108affected
- 4.4.0 and later · before 4.4.0.72affected
- 4.5.0 and later · before 4.5.0.57affected
- 4.6.0 and later · before 4.6.0.21affected
WSO2 WSO2 Carbon API Manager Rest API Utility
- 9.20.74 and later · before 9.20.74.401affected
- 9.28.116 and later · before 9.28.116.417affected
- 9.29.120 and later · before 9.29.120.236affected
- 9.30.67 and later · before 9.30.67.167affected
- 9.31.86 and later · before 9.31.86.158affected
- 9.32.147 and later · before 9.32.147.59affected
- 9.33.106 and laternot affected
WSO2 WSO2 Traffic Manager
- 4.5.0 and later · before 4.5.0.56affected
- 4.6.0 and later · before 4.6.0.21affected
WSO2 WSO2 Universal Gateway
- 4.5.0 and later · before 4.5.0.57affected
- 4.6.0 and later · before 4.6.0.21affected
Same product
wso2: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-1728Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover39Monitor
- CVE-2025-9312Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products39Monitor
- CVE-2025-9152Improper Privilege Management in Multiple WSO2 API Manager via keymanager-operations DCR Endpoint39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-8591Jul 6, 2026 · Reflected Cross-Site Scripting via URL Parameter in Multiple WSO2 Products Enables UI Modification24Monitor
- ← EarlierCVE-2026-2445Jul 20, 2026 · Reflected Cross-Site Scripting via URL Parameter in Multiple WSO2 Products Enables UI Redirection and Modification24Monitor
- Later →CVE-2024-10302Aug 6, 2026 · Improper Input Validation via Signup Process in Multiple WSO2 Products Enables Content Manipulation and Data Exposure23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Proof-of-concept repository on GitHub ×4
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-09-16 |
| Proof-of-concept repository on GitHub | stars:2 | 2026-09-25 |
| Proof-of-concept repository on GitHub | stars:1 | 2026-10-08 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-08 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+41 d
- CISA KEV+49 d
- TodayNov 11, 2026+97 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- hacktron.aifinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
—
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2025-1273728 days apartArbitrary Code Execution via Administrative Operations in Multiple WSO2 Products Allows Remote Code Execution33Monitor
- CVE-2025-13590168 days apartAuthenticated arbitrary file upload via a System REST API requiring administrator permission.28Monitor
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, {
algorithms: ["RS256"],
issuer: "https://id.example.com",
audience: "portal",
});Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.