How to check if you are exposed to CVE-2026-5430
- Find every WSO2 Multiple Products system you or your clients run, including ones exposed to the internet. Those come first: CISA only lists flaws attackers are already using.
- Compare each version with the fixed versions in the vendor advisory below. Where no fix exists yet, apply the vendor’s mitigation or take the system off the internet.
- Run a credentialed vulnerability scan to catch the systems you missed, then check that the next scan no longer reports CVE-2026-5430.
US federal agencies had to fix this by 2026-09-27. Everyone else should treat that deadline as a guide: if it has passed, this is overdue.
Affected versions
Versions the National Vulnerability Database lists as vulnerable to CVE-2026-5430. Check the vendor advisory for the exact fixed builds before you sign anything off.
| Product | Vulnerable versions |
|---|---|
| WSO2 API Control Plane | from 4.5.0 before 4.5.0.58; from 4.6.0 before 4.6.0.22 |
| WSO2 API Manager | from 4.1.0 before 4.1.0.257; from 4.2.0 before 4.2.0.197; from 4.3.0 before 4.3.0.108; from 4.4.0 before 4.4.0.72; from 4.5.0 before 4.5.0.57; from 4.6.0 before 4.6.0.21 |
| WSO2 Traffic Manager | from 4.5.0 before 4.5.0.56; from 4.6.0 before 4.6.0.21 |
| WSO2 Universal Gateway | from 4.5.0 before 4.5.0.57; from 4.6.0 before 4.6.0.21 |
Timeline
- · Published in the National Vulnerability Database
- · Added to CISA's Known Exploited Vulnerabilities catalog, 49 days after it was published
- · Fix-by date for US federal agencies, passed 35 days ago
Vendor advisories and fixes
Weakness type
More exploited WSO2 vulnerabilities
CISA lists 2 exploited WSO2 vulnerabilities. The closest matches:
Keep going
Sources: CISA Known Exploited Vulnerabilities catalog (version 2026.10.30); EPSS data from FIRST.org; CVSS and descriptions from the NIST National Vulnerability Database. Checked 2026-11-01. This product uses the NVD API but is not endorsed or certified by the NVD.
