← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2026-5430 exploited? Yes: in CISA KEV since 24 Sep 2026

Gociux · WSO2 Multiple Products · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2026-5430, WSO2 Multiple Products Path Traversal Vulnerability , is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 24 Sep 2026, 49 days after it was published. It affects WSO2 Multiple Products. If you run it, CISA's required action is: 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.

exploitedYesCISA KEV · 24 Sep 2026
ransomwareNot knownno confirmed use
EPSStop 5%very likely to be exploited
severity10CVSS 3.1 · critical
US federal due27 Sep 2026BOD 22-01 deadline

What it is

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.

VendorWSO2 (2 exploited CVEs in KEV)
ProductMultiple Products
VulnerabilityWSO2 Multiple Products Path Traversal Vulnerability
WeaknessCWE-347
Published6 Aug 2026
Added to KEV24 Sep 2026
Reported by (CNA)WSO2

What to do

  1. Check whether you run it. Look for Multiple Products in your asset inventory, including appliances and cloud images. Stack check lists every exploited WSO2 CVE at once.
  2. Apply the fix. 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.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 6 Aug 2026.
  4. Get told next time. Email alerts when CISA adds a CVE for WSO2.

Other exploited CVEs in Multiple Products

References

Questions

Is CVE-2026-5430 being exploited?

Yes. CISA added CVE-2026-5430 to the Known Exploited Vulnerabilities catalog on 24 Sep 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2026-5430 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2026-5430?

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. Check WSO2's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Multiple Products and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in September 2026 · WSO2 scorecard · act-now radar.

Running WSO2 in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →