KEV Lag Tracker → CVE-2026-5430. Data verified against the official CISA KEV catalog and the National Vulnerability Database.

CISA added CVE-2026-5430 (WSO2 Multiple Products) to the Known Exploited Vulnerabilities catalog on September 24, 2026. It was publicly known for 49 days before CISA confirmed active exploitation. A KEV listing is CISA’s official confirmation that a vulnerability is being exploited in the wild.

The Record

CVECVE-2026-5430
Vendor / productWSO2 Multiple Products
VulnerabilityWSO2 Multiple Products Path Traversal Vulnerability
CVSS base score10
EPSS probability the day before the KEV listing0.32% (25.4% percentile)
NVD publication dateAugust 6, 2026
Added to CISA KEVSeptember 24, 2026
Lag (public → KEV listing)49 days
Federal patch deadlineSeptember 27, 2026
Known ransomware useNo

Measured against the 1734 entries in our tracker with verified publication dates, CVE-2026-5430 was flagged faster than 64% of them.

What CISA Reported

CISA describes the flaw as follows: “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. ”

Federal Patch Deadline

Under Binding Operational Directive rules, U.S. federal agencies must remediate CVE-2026-5430 by September 27, 2026 — a 3-day remediation window from the KEV listing date. Private organizations are not bound by that deadline; CISA treats it as the benchmark for how urgently a confirmed-exploited flaw should be patched.

What EPSS Forecast Before the Confirmation

The EPSS forecast (FIRST’s daily estimate of the probability a CVE will be exploited within 30 days) put CVE-2026-5430 at 0.32% on the day before CISA confirmed active exploitation — the 25.4% percentile of all scored CVEs that day. That places it outside the top 10% of EPSS risk on the eve of confirmation — a patch queue ordered by EPSS alone would have left it for later.

EPSS for CVE-2026-5430Value
Probability the day before the KEV listing0.32%
Percentile the day before the KEV listing25.4%
Probability today (October 8, 2026)0.59%
Percentile today46.5%

Today’s figure is not evidence that the forecast worked: EPSS reacts to the KEV listing itself, so the score for any confirmed-exploited CVE tends to rise after CISA acts. Only the eve-of-listing number was available to a defender making the call. Across every KEV entry we track, we measured how often that number was high — see the EPSS accuracy analysis.

How This Compares

We do not yet track enough WSO2 entries to publish a vendor median (the threshold is five with verified publication dates), so the reference here is the catalog as a whole:

Across all tracked KEV entriesValue
Entries with verified publication dates1734
Median lag (disclosure → KEV listing)245 days
Exploited within 7 days of disclosure25%
Tied to known ransomware campaigns19%

Frequently Asked Questions

What is CVE-2026-5430?

CVE-2026-5430 is a vulnerability in WSO2 Multiple Products (WSO2 Multiple Products Path Traversal Vulnerability ) that CISA added to its Known Exploited Vulnerabilities catalog on September 24, 2026. A KEV listing is CISA’s official confirmation that the flaw is being exploited in the wild.

How long was CVE-2026-5430 public before CISA confirmed exploitation?

49 calendar days, measured from its NVD publication date to the date CISA added it to the KEV catalog.

What is the federal patch deadline for CVE-2026-5430?

U.S. federal agencies must remediate CVE-2026-5430 by September 27, 2026, a 3-day window from the KEV listing date. Private organizations are not bound by that deadline, but CISA treats it as the benchmark for how urgently a confirmed-exploited flaw should be patched.

Is CVE-2026-5430 used in ransomware campaigns?

CISA has not flagged CVE-2026-5430 as known to be used in ransomware campaigns. That field reflects confirmed campaign use, not the absence of risk.

What was the EPSS score for CVE-2026-5430 before it was confirmed as exploited?

0.32% — the probability EPSS assigned on the day before CISA added CVE-2026-5430 to the KEV catalog, placing it in the 25.4% percentile of all scored CVEs that day. That is outside the top 10% of EPSS risk. Its score today is higher in most cases because EPSS reacts to the KEV listing itself, so only the eve-of-listing figure reflects what a defender could have acted on.

Is a 49-day lag typical?

The median across all 1734 KEV entries we track with verified publication dates is 245 days, so CVE-2026-5430 is below the catalog median.

Related Coverage

Primary Sources

How We Track This

This page is generated from our CISA KEV Lag Tracker, which syncs the official CISA KEV catalog daily and records the date each CVE is added. For every entry we retrieve the original NVD publication date and compute the lag in calendar days. No date or figure on this page is estimated or taken from a third-party source — they come directly from CISA and NVD records. Free to cite with attribution to CVEDaily (CC BY 4.0).