CVE-2026-5430
Last modified
CVE-2026-5430 is a critical-severity vulnerability rated 10/10 on the CVSS scale. 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. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Wso2 | Api Control Plane | >= 4.5.0, < 4.5.0.58 |
| Wso2 | Api Control Plane | >= 4.6.0, < 4.6.0.22 |
| Wso2 | Api Manager | >= 4.1.0, < 4.1.0.257 |
| Wso2 | Api Manager | >= 4.2.0, < 4.2.0.197 |
| Wso2 | Api Manager | >= 4.3.0, < 4.3.0.108 |
| Wso2 | Api Manager | >= 4.4.0, < 4.4.0.72 |
| Wso2 | Api Manager | >= 4.5.0, < 4.5.0.57 |
| Wso2 | Api Manager | >= 4.6.0, < 4.6.0.21 |
| Wso2 | Traffic Manager | >= 4.5.0, < 4.5.0.56 |
| Wso2 | Traffic Manager | >= 4.6.0, < 4.6.0.21 |
| Wso2 | Universal Gateway | >= 4.5.0, < 4.5.0.57 |
| Wso2 | Universal Gateway | >= 4.6.0, < 4.6.0.21 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-5430?
How severe is CVE-2026-5430?
How do I fix CVE-2026-5430?
How Strix Helps
- Same Subject, Wrong User: A Cross-Issuer Account Takeover in n8nStrix found an identity-binding bug in n8n's token-exchange flow enabling account takeover.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-54294Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMB…
- CVE-2026-54295Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMB…
- CVE-2026-54296Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMB…
- CVE-2026-54297Faraday is an HTTP client library abstraction layer that pro…7.5
- CVE-2026-54298Astro is a web framework. Prior to 6.4.6, the spreadAttribut…6.1
- CVE-2026-54299Astro is a web framework. Prior to 6.4.6, Astro SSR apps wit…7.5
- CVE-2026-54300@astrojs/netlify is an adapter that allows Astro to deploy y…5.3
- CVE-2026-54301n8n is an open source workflow automation platform. Prior to…5.4
- CVE-2026-54302n8n is an open source workflow automation platform. Prior to…5.4
- CVE-2026-54303n8n is an open source workflow automation platform. Prior to…5.4
- CVE-2026-54304n8n is an open source workflow automation platform. Prior to…7.7
- CVE-2026-54305n8n is an open source workflow automation platform. Prior to…9.9
Are you affected by CVE-2026-5430?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
