~/exploited / cve-2026-5430
CVE-2026-5430: WSO2 Multiple Products
According to CISA this vulnerability is already used in attacks (added on 24 September 2026).
Key facts
| CVE | CVE-2026-5430 |
|---|---|
| Vendor | WSO2 — Multiple Products |
| Vulnerability | WSO2 Multiple Products Path Traversal Vulnerability |
| Added | 24 September 2026 |
| Deadline (US agencies) | 27 September 2026 |
| Ransomware campaigns | unknown |
Technical data (NVD, FIRST EPSS)
| CVSS base score | 10.0 (critical) · CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HAttack over the network, complexity: low, privileges: none needed, user interaction: none |
|---|---|
| EPSS (exploitation probability) | Probability of exploitation in the next 30 days: 78.84%. Higher than 99.6% of all scored vulnerabilities (as of 18 November 2026). A high value means attacks are very likely and often already widespread. |
| Weakness type (CWE) | CWE-347 |
| Affected versions | api control plane: >= 4.5.0, < 4.5.0.58 api control plane: >= 4.6.0, < 4.6.0.22 api manager: >= 4.1.0, < 4.1.0.257 api manager: >= 4.2.0, < 4.2.0.197 api manager: >= 4.3.0, < 4.3.0.108 api manager: >= 4.4.0, < 4.4.0.72 api manager: >= 4.5.0, < 4.5.0.57 api manager: >= 4.6.0, < 4.6.0.21 and 4 more |
Description (NVD)
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.
Patches and vendor advisories
Description (CISA)
WSO2 API Control Plane, API Manager, Traffic Manager & Universal Gateway contain a path traversal vulnerability that could allow for unrestricted file upload and lead to remote code execution.
Required action (CISA)
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.
What admins should do now
- Affected? Check whether WSO2 Multiple Products is in use and which version runs (package manager, admin UI,
--version). - Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
- Review logs back to 24 September 2026: unusual logins, new files, unexpected processes, outbound connections.
- If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.
The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.
Sources
- CISA KEV Catalog
- NVD CVE-2026-5430
- security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026
- www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-base
- www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizi
- nvd.nist.gov/vuln/detail/CVE-2026-5430
New articles by e-mail
One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).