The floor opened under Cisco Catalyst SD-WAN controllers in May. CVE-2026-20182 — CVSS 10.0, pre-auth, network-accessible, scope-changed, full C/I/A — has been under active exploitation for 24 days with no confirmed patch. The Register put it plainly on June 5: "Yet another Cisco SD-WAN 0-day under attack, and no patch in sight." The "yet another" is The Register being generous.
This is not a UI flaw or an ancillary service. The vulnerability lives in the peering authentication handshake — the core control-plane authentication mechanism. An unauthenticated attacker sends crafted requests to that endpoint, receives an authenticated session as a high-privileged internal account, and then has NETCONF access to the entire SD-WAN fabric. Routing policy, BGP routes, firewall rules, VPN topology — all of it. That's not a foothold. That's the keys to the building.
CISA issued Emergency Directive 26-03 on May 14 — the same day this hit the KEV catalog. ED designations are reserved for threats requiring immediate federal action, distinct from the standard KEV process. The federal remediation deadline was May 17. Three days. That deadline is now 21 days overdue, and there is still no vendor patch confirmed.
The scope-changed CVSS vector (S:C) is the detail that matters most for blast radius. A successful exploit doesn't stay contained to the controller — it propagates across the SD-WAN fabric. For any enterprise running Cisco SD-WAN as the backbone of branch connectivity, remote-site VPNs, or cloud on-ramp, this is a full-fabric exposure from a single unauthenticated request. CWE-287. No credentials required. No user interaction. No complex chaining.
Cisco's own advisory notes CVE-2026-20182 "was discovered and fixed after the [February 2026 disclosure] was disclosed" — meaning the patch process for a prior SD-WAN flaw surfaced a related but distinct vulnerability in the same authentication mechanism. The same code path, visited twice. Predictable in retrospect.
EPSS data is absent — the model hasn't scored this yet, almost certainly due to recency. With CVSS 10.0, KEV-listed, active exploitation confirmed, and a CISA Emergency Directive in play, the percentile is not in question. Don't wait for the score.
On lifecycle: every automated model currently anchors this at Discovered (97.5%), based on two observations — KEV add and NVD publish. That is a model artifact. The Register's active exploitation reporting isn't yet reflected. Real-world state is almost certainly Weaponized to Mass Exploitation. Treat the model probability as noise for this CVE.
The MITRE picture is clean and severe: T1190 (Exploit Public-Facing Application) into T1078.001 (Valid Accounts: Default/Internal) via the auth bypass, then T1602 (Network Device Configuration Dump) and T1059.008 (Network Device CLI) through NETCONF, with T1562.004 (Disable or Modify System Firewall) as the immediate downstream capability. That chain runs without a single credential.
Since no patch exists, compensating controls are the only path right now. Restrict management-plane access to known admin IP ranges via ACL — the peering authentication endpoint should not be reachable from arbitrary network sources. Run the CISA ED 26-03 Hunt & Hardening Guidance, which includes specific Show Control Connections CLI commands to detect anomalous authenticated sessions. Audit all active NETCONF connections on Controllers and Managers for sessions that cannot be attributed to known admin activity. When Cisco ships a fix, it goes in that night.
If you're a federal agency or federal contractor: May 17 has passed. Document compensating controls immediately. Any unpatched SD-WAN controller should be treated as compromised until proven otherwise.