Wso2 Api Control Plane
CVE-2026-5430
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.
What this means for your business
- It affects Wso2 Api Control Plane. It matters if your company, or a supplier that handles your data, runs it.
- Attackers are already using it. CISA added it to its list of flaws used in real attacks on 24 September 2026.
- An attacker can use it remotely, over a network, without a login, and without anyone at your company clicking anything.
- FIRST's prediction model gives it a 0.4% chance of attack attempts being seen in the next 30 days, ranking above 28% of all known flaws.
What to do
- 1Check whether your company or your suppliers run Wso2 Api Control Plane, and which version. The affected versions are listed further down this page.
- 2If you do, apply the vendor's fix. A patch or vendor advisory has been published.
- 3Treat it as urgent. US federal agencies must fix it by 27 September 2026. That deadline does not apply to private companies, but it shows how seriously CISA takes it.
- 4Because attackers have used it, check the affected systems for signs of a break-in, not only for the update.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
Required action
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.
CISA’s wording, unedited. The notes it mentions are in CISA’s catalogue entry.
Scoring
- CVSS
- 10.0 (v3.1)
- Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H- Weakness
- CWE-347
- Assigned by
- ed10eef1-636d-4fbe-9993-6890dfa878f8
Dates
- Published
- 2026-08-06
- Last modified
- 2026-09-25
- Added to KEV
- 2026-09-24
- Remediation due
- 2026-09-27
- Sources
- CISA KEV, NVD
Affected products
- Wso2 Api Control Plane4.5.0 - 4.5.0.58, 4.6.0 - 4.6.0.22
- Wso2 Api Manager4.1.0 - 4.1.0.257, 4.2.0 - 4.2.0.197, 4.3.0 - 4.3.0.108, 4.4.0 - 4.4.0.72, 4.5.0 - 4.5.0.57, 4.6.0 - 4.6.0.21
- Wso2 Traffic Manager4.5.0 - 4.5.0.56, 4.6.0 - 4.6.0.21
- Wso2 Universal Gateway4.5.0 - 4.5.0.57, 4.6.0 - 4.6.0.21
As listed in the NVD configuration data. Not a statement about your estate.
Coverage
- WSO2 and Adobe Commerce Flaws Exploited in Attacks, Added to CISA KEVThe Hacker News · 2026-09-25