CVE-2026-5430 is an improper cryptographic-signature-verification vulnerability in JWT authentication in WSO2 API Manager, API Control Plane, Traffic Manager, and Universal Gateway. Affected implementations can accept and validate JWTs signed with algorithms other than the explicitly configured or supported algorithms. An unauthenticated attacker can therefore submit a forged JWT using an unsupported algorithm to bypass authentication. Affected releases include API Manager 4.1.0 through 4.6.0 before their respective fixed update levels; API Control Plane 4.5.0 and 4.6.0 before fixed updates; Traffic Manager 4.5.0 and 4.6.0 before fixed updates; and Universal Gateway 4.5.0 and 4.6.0 before fixed updates.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
33 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical, unauthenticated remote authentication-bypass vulnerability in WSO2 API-management products. An attacker can submit a JWT signed using an unsupported algorithm to bypass authentication, access protected functions, and potentially take over privileged or administrative accounts.
A critical, remotely exploitable JWT authentication-bypass flaw in WSO2 API management products. An unauthenticated attacker can use a token signed with an unsupported algorithm to bypass authentication, access protected functions, and potentially take over privileged or administrative accounts.
A maximum-severity (CVSS 10) WSO2 JWT authentication-bypass vulnerability. Attackers can use a forged JWT signed with an unsupported algorithm to obtain unauthorized access, potentially compromise administrative accounts, take over accounts, access API backend endpoints and credentials, and intercept sensitive data transiting affected API infrastructure.
Critical JWT authentication-bypass/account-takeover vulnerability caused by improper verification of cryptographic signatures. The affected WSO2 services accept JWTs signed with unsupported algorithms and approve them, allowing forged privileged tokens to access API backends, application credentials, consumer keys, and secrets.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.