CVE-2026-5430Critical· 10.0▾ Hadal⚠ Exploited in the wildPoC availableThe 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, leadin…
▾ Hadal zone — Critical and actively exploited (CISA KEV / 0day)
impact 55 · likelihood 0.1 · exploitation 25
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Public exploit / PoC code seen in 1 source. Availability, not in-the-wild use.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Sep 24.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via NVD
Federal remediation due Sep 27, 2026
0.4%
Last analysed / modified upstream
1 GitHub repo (last check)
Added to the CISA catalog on Sep 24, 2026. Federal remediation due Sep 27, 2026. View catalog ↗
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.
api_control_plane >= 4.5.0, < 4.5.0.58api_control_plane >= 4.6.0, < 4.6.0.22api_manager >= 4.1.0, < 4.1.0.257api_manager >= 4.2.0, < 4.2.0.197api_manager >= 4.3.0, < 4.3.0.108api_manager >= 4.4.0, < 4.4.0.72api_manager >= 4.5.0, < 4.5.0.57api_manager >= 4.6.0, < 4.6.0.21traffic_manager >= 4.5.0, < 4.5.0.56traffic_manager >= 4.6.0, < 4.6.0.21universal_gateway >= 4.5.0, < 4.5.0.57universal_gateway >= 4.6.0, < 4.6.0.21Upgrade past the affected range:
api_control_plane 4.6.0.22api_manager 4.6.0.21traffic_manager 4.6.0.21universal_gateway 4.6.0.21Connected by shared product, vendor, weakness, or advisory.
CVE-2026-3416Medium· 5.9The API Publisher component previously used a non-cryptographic pseudorandom number generator (PRNG) to create shared secrets for Webhook HMAC validation
CVE-2025-12737High· 8.4The administrative operations within the Carbon Console do not adequately validate specific user-supplied input
CVE-2024-6832Medium· 5.9The account locking mechanism fails to trigger when secondary user stores are inaccessible
CVE-2024-10302Medium· 4.0The user self-signup flow in multiple WSO2 products fails to adequately validate user-supplied input
CVE-2026-1529High· 8.1A flaw was found in Keycloak
CVE-2026-3418Critical· 9.1Arbitrary File Upload via System REST API in Multiple WSO2 Products Allows Remote Code Execution