3AUG

CISA gives Cisco SD-WAN three days to patch

3 min read

16:08UTC

On 20 April, CISA added three Cisco Catalyst SD-WAN Manager CVEs to the KEV catalogue with a three-day federal remediation deadline of 23 April.

← Back to KEV deadlines fell from 14 days to three Jump to analysis ↓

TechnologyDeveloping

Key takeaway

Three days for SD-WAN patches against the same vendor whose perimeter line is below the patch layer.

CISA added three Cisco Catalyst SD-WAN Manager vulnerabilities to the Known Exploited Vulnerabilities (KEV) catalogue on Monday 20 April with a three-day federal remediation deadline, the shortest of the window ¹. CVE-2026-20122 is an API privilege escalation; CVE-2026-20133 is sensitive information exposure; CVE-2026-20128 is a password storage flaw. All three sit in Cisco's software-defined wide-area network management plane, the orchestrator that pushes policy to branch-office routers across an enterprise estate.

KEV catalogue size has now reached 1,585 entries with 16 additions in the thirteen-day window, running at roughly 1.2 per day. The same emergency cadence applied to CitrixBleed 3 on 23 March and to the F5 BIG-IP APM reclassification on 14 April . The pace has not slowed despite the proposed FY27 CISA budget cut ; the operational tempo is being held against a workforce reduction.

The contrast with the FIRESTARTER cluster is what changes the CISO's procurement maths. The same vendor whose ASA and Firepower line hosts a nation-state-tier implant below the patch layer also has an SD-WAN trio caught by fast patching against opportunistic-tier actors. CISA's SD-WAN deadline shows the patching tier still functioning against opportunistic actors, while AA26-113A shows the eviction tier failing against the FIRESTARTER actor. For any organisation buying Cisco for both perimeter security and SD-WAN, the two stories converge on the same change-control queue: SD-WAN devices need to be patched on a stopwatch, and ASA devices need to be unplugged and audited from cold start. The single-vendor stack conversation gets harder in that week.

Deep Analysis

In plain English

Cisco's SD-WAN Manager is the control system that tells a company's branch-office routers what to do. Three security flaws in that control system were added to a US government emergency list, and federal agencies were given just three days to fix them. Three days is unusually short: it signals the government had evidence that hackers were already actively exploiting these flaws against real targets, not running exploratory probes.

Deep Analysis

Root Causes

Cisco Catalyst SD-WAN Manager is the centralised policy orchestrator for software-defined wide-area networks. Its API privilege escalation, information exposure, and password storage vulnerabilities sit at the intersection of two structural problems: the management plane is accessible from enterprise network segments that also carry user traffic, and the SD-WAN Manager's elevated privilege means a single compromised credential produces network-wide policy control.

The SD-WAN Manager also sits inside the same change-control queue as the perimeter firewalls whose patch cycle FIRESTARTER exploited. The shortest KEV deadline of the window signals that exploitation of these CVEs produces immediate enterprise-wide impact rather than limited device-specific impact.

What could happen next?

Consequence
Any enterprise running Cisco Catalyst SD-WAN Manager needs emergency change control for three CVEs simultaneously, adding to the existing ASA/Firepower cold-start audit burden from the FIRESTARTER cluster.
Risk
Organisations that process Cisco SD-WAN patches on the standard 30-day enterprise change-control cycle will remain exposed to confirmed active exploitation for weeks after the KEV deadline.

Source Landscape

This story draws on neutral-leaning sources

Primary parallel: CISA applied a comparable compressed deadline to the Fortinet SSL VPN zero-day chain in January 2024 (CVE-2024-21762), where exploitation was confirmed within 72 hours of disclosure and the agency set a 48-hour federal deadline.

Fortinet's management plane vulnerability class is structurally parallel to the Cisco SD-WAN Manager CVEs: both sit in the network orchestration layer that pushes policy to enterprise branch infrastructure, and both allow a remote attacker to pivot from the management plane to the full branch network without additional credentials.

Counter-parallel: The 2021 Pulse Secure VPN zero-day (CVE-2021-22893) was added to CISA's predecessor watchlist with a 21-day remediation window despite confirmed nation-state exploitation of US defence contractors. The difference with the April 2026 Cisco SD-WAN window is that compressed deadlines are now the norm, not the exception, which means organisations that have built patch scheduling around historical deadline norms are systematically behind the current operational tempo.

Consensus view: The Cybersecurity Policy Program at George Washington University's Institute for Cyber Security and Privacy notes that CISA's three-day federal deadline for the Cisco SD-WAN trio is the shortest KEV remediation window applied to a Cisco product line since the programme's inception.

At 1,585 total entries, the KEV catalogue has grown to a size where the deadline compression signals live exploitation urgency rather than precautionary escalation: CISA only shortens windows when in-the-wild exploitation activity is confirmed, not merely probable.

Counter-view: Citizens Lab's technology policy team argues that the KEV's binding authority covers only federal civilian agencies and has no direct enforcement mechanism over private critical infrastructure operators, where most Cisco Catalyst SD-WAN Manager deployments sit.

The practical effect of the three-day deadline is a signalling exercise for private-sector patch prioritisation, not a mandated remediation cycle. CISA's proposed FY27 budget cut compounds this: the agency is issuing an accelerating volume of urgent advisories with a diminishing workforce to monitor compliance.

Key tension: Whether the KEV programme can sustain its enforcement credibility when the volume of additions (16 in 13 days) outpaces any realistic federal patching capacity, particularly against a backdrop of workforce reduction.

Sources:CISA

Mentions:CISA →Cisco Catalyst SD-WAN Manager →Cisco →FIRESTARTER →AA26-113A →Washington →CitrixBleed 3 →Fortinet →Aker ASA →F5 BIG-IP Access Policy Manager →Known Exploited Vulnerabilities →

First Reported In

Update #2 · FIRESTARTER puts Cisco below the patch line

CISA· 30 Apr 2026

Read original →

Causes and effects

Caused by

CitrixBleed 3 lands on SAML broker

CISA three-day Cisco SD-WAN deadline follows the same emergency-KEV cadence previously applied to CitrixBleed 3 in ID:2544.

Occurred 23 Mar 2026

Read story →

F5 reclassifies DoS bug to 9.8 RCE

Cisco SD-WAN KEV addition repeats the emergency-remediation pattern from F5 BIG-IP APM reclassification in ID:2545.

Occurred 28 Mar 2026

Read story →

CISA deadline for PAN-OS RCE lands four days early

CISA's deadline-before-patch for PAN-OS extends the three-day standard first applied to Cisco SD-WAN Manager, where the patch existed at KEV-add time.

Occurred 6 May 2026

Read story →

This Event

CISA gives Cisco SD-WAN three days to patch

The shortest KEV deadline of the window shows the patching tier still works against opportunistic actors, against the same vendor whose perimeter line is hosting an unpatched implant.

Different Perspectives

Group-IB

Group-IB, headquartered in Singapore, documented on 19 March that The Gentlemen began inside Qilin's own affiliate programme and split from it over a payment dispute. Its analysis makes this window's leak-site tally readable as a fracture inside one ransomware operation rather than the arrival of an unknown crew.

ENISA

ENISA placed EU drinking water and wastewater in its cyber risk zone for the first time on 28 May, finding one in three water entities had never run a risk assessment. CISA's 30 July advisory to American operators reads as the operational sequel to a gap European regulators had already documented two months earlier.

House of Lords and NCSC

The Cyber Security and Resilience Bill sits at House of Lords committee stage, its amendment paper running to 23 July. Separately, the NCSC guidance CISA cited when directing water operators to disconnect controllers is version 1.0 from March 2024, a two-year-old British document doing operational work in an American alert published last week.

heise online

heise online reported on 27 July that Russian state attackers, named as APT28, ran the hotel WiFi credential-harvesting campaign. Its attribution is firmer than ReliaQuest's own hedged low-to-medium confidence assessment of the same intrusion, a difference in national reporting posture rather than a settled dispute over who is responsible.

CISA and ReliaQuest

CISA compressed remediation deadlines under BOD 26-04 while, in the same window, telling water and wastewater operators to disconnect internet-exposed controllers rather than patch them. ReliaQuest, investigating the hotel WiFi campaign, held its assessment of the intrusion route at low-to-medium confidence and declined to name a state sponsor.

AIVD

AIVD co-signed AA26-204A alongside CISA, the NSA and the FBI, adding its signature to the fifteen-agency coalition naming LAUNDRY BEAR. Dutch involvement continues a pattern of joint Five Eyes-adjacent advisories the agency has co-issued with CISA and NCSC through 2026.