CVE-2026-5430
WSO2 Multiple Products Path Traversal Vulnerability
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.
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Deadline for federal agencies: 2026-09-27.
6 articles across 4 outlets · first covered Jun 30, 2026 · latest Sep 25, 2026
Coverage timeline
-
CISA Flags Critical WSO2 and Magento Flaws Used in Attackssecurityaffairs.com · Sep 25, 2026
-
CISA Warns of Exploited WSO2 and Adobe Commerce Flawssecurityonline.info · Sep 25, 2026
-
CISA Warns of Active Exploits Targeting Critical WSO2 Flawcisa.gov · Sep 24, 2026
-
Critical WSO2 Flaw Exploited to Steal API Credentials and Secretswww.securityweek.com · Sep 16, 2026
-
WSO2 Flaws Enable Account Takeover Via JWT Bypass, Patch Urgedsecurityonline.info · Aug 7, 2026
-
WSO2 patches critical JWT bypass flaw, putting bank APIs at risksecurityonline.info · Jun 30, 2026