CVE-2026-5430

WSO2 Multiple Products remote code execution, confirmed exploited in the wild.

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.

Check your domain free How we watch for this

22%chance of exploitation in the next 30 days (EPSS), 97th percentile

24 Sepadded to CISA's Known Exploited Vulnerabilities list, 2026

27 Sepfederal remediation deadline, already passed

Passedpast the deadline: patch now

CISA's name for it	WSO2 Multiple Products Path Traversal Vulnerability
Vendor and product	WSO2 · Multiple Products
Type	remote code execution · CWE-347
Exploited	Confirmed by CISA listed 24 September 2026
Likelihood	one of the most likely to be exploited of every vulnerability tracked
Deadline	27 September 2026 · already passed
Used in ransomware	Not reported
Advisories	security.docs.wso2.com ↗ · www.cisa.gov ↗ · www.cisa.gov ↗ · nvd.nist.gov ↗

What to do

Three steps, in this order

Step 1

Patch to the fixed version the vendor names, today if the product faces the internet.

Step 2

Until it is patched, take the affected service off the internet or put it behind a VPN or allow-list.

Step 3

Look for signs it was already used: new accounts, web shells, unexpected processes and outbound connections since the date it was listed.

CISA's 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 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.

Is it on your estate?

Know before someone else finds it

Threat Landscape Monitoring fingerprints the software your internet-facing hosts disclose and matches it, every day, against this list and the exploitation scores. When a new entry touches something you run, you are told once, with the host and the fix. The free plan covers one domain.

Start free with one domain Run the free domain check

Questions

CVE-2026-5430 in short

Is CVE-2026-5430 being exploited?

Yes. CISA added CVE-2026-5430 to its Known Exploited Vulnerabilities catalogue on 24 September 2026, which it does only on evidence of exploitation in the wild.

What is the CISA deadline for CVE-2026-5430?

US federal agencies must remediate it by 27 September 2026. Everyone else should treat that date as the latest safe point to patch an internet-facing system.

How likely is CVE-2026-5430 to be exploited in the next 30 days?

FIRST's Exploit Prediction Scoring System gives it 22%, the 97th percentile of every CVE it scores.

How do I fix CVE-2026-5430?

Patch to the fixed version the vendor names, today if the product faces the internet. Until it is patched, take the affected service off the internet or put it behind a VPN or allow-list. Look for signs it was already used: new accounts, web shells, unexpected processes and outbound connections since the date it was listed.

Sources: CISA Known Exploited Vulnerabilities catalogue (released 10 November 2026) and FIRST EPSS. Page compiled automatically by SAK T.L.M, the threat-intelligence tool of SAK T.E.C, on 13 November 2026.