Exploited CVEs / CVE-2026-5430
CVE-2026-5430
WSO2 Multiple Products Path Traversal Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-09-27 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.
Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.
Risk summary
Actively exploited WSO2 Multiple Products vulnerability, Critical severity, CVSS v3 10.0. Added to the CISA KEV catalog 2026-09-24.
Updated September 24, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Senserva AI Opinion for CVE-2026-5430
CVE-2026-5430 is a path traversal flaw in WSO2 API Control Plane, API Manager, Traffic Manager and Universal Gateway that permits unrestricted file upload and can end in remote code execution. It carries Critical Severity at CVSS 10.0 and CISA added it to the KEV catalog on 2026-09-24, so exploitation is confirmed rather than theoretical, even though no ransomware use is known. Anyone running these WSO2 components as API gateways is exposed, and these systems often sit at the network edge, which makes a compromise a likely foothold into backend services.
Do this: Identify every WSO2 API Control Plane, API Manager, Traffic Manager and Universal Gateway instance you run, apply the vendor's patch today, and review those hosts for unexpected uploaded files or new web shells.
AI-generated from public data, 2026-11-10. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2026-5430
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2026-5430
- Published
- 2026-09-24
- Last revised
- 2026-09-24
- Changes tracked
- 1
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
CISA added CVE-2026-5430 to its KEV catalog on 2026-09-24, the strongest signal here, since it confirms active exploitation. EPSS stayed near 0.6% for a month, then jumped to 22.4% on 2026-10-25. The late surge suggests exploitation is spreading or becoming easier, so treat patching today as a priority rather than waiting.
Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.
- 2026-09-24 EPSS first scored at 0.4%; added to the CISA KEV catalog by CISA
- 2026-09-25 EPSS 0.4% to 0.6%
- 2026-09-26 EPSS 0.6% to 0.6%
- 2026-10-25 EPSS 0.6% to 22.4%
Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.
CISA required action
Federal remediation due date: 2026-09-27 (past due).
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.
Official fix for CVE-2026-5430
Update WSO2 API Control Plane to version 4.5.0.58 or later. Update WSO2 API Control Plane to version 4.6.0.22 or later. Update WSO2 API Manager to version 4.1.0.257 or later. (Fixed-version data from NVD.)
Common questions about CVE-2026-5430
Is CVE-2026-5430 actively exploited?
Yes. CVE-2026-5430 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-09-24, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 22%.
What is the CISA deadline and required action for CVE-2026-5430?
CISA set the federal remediation due date at 2026-09-27, which has passed; treat any unremediated system as overdue. The verbatim 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.
What fixes CVE-2026-5430?
Check the vendor's security advisory for the patched Multiple Products versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2026-5430?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-5430's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed daily (early morning US Central).
Scope and sources
- More exploited WSO2 CVEs
- Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.