CVE-2026-20182: Cisco Catalyst SD-WAN peering authentication bypass (CVSS 10.0) exploited by UAT-8616; affects Controller, Manager and Validator
A forged vHub peer can plant an SSH key on Cisco SD-WAN controllers without credentials; Talos ties exploitation to UAT-8616
Analysis
CVE-2026-20182 (CVSS 10.0, CWE-287) is an authentication bypass in the peering authentication of Cisco Catalyst SD-WAN Controller, Manager and, since Cisco's advisory revision of 2026-06-16, Validator, affecting all deployment types regardless of configuration (Cisco PSIRT). Rapid7 showed the mechanism on the Controller: the vdaemon DTLS control-plane service on UDP/12346 accepts a CHALLENGE_ACK claiming device type 2 (vHub) from a self-signed peer without verifying it, after which message type 14 (MSG_VMANAGE_TO_PEER) appends an attacker SSH key to /home/vmanage-admin/.ssh/authorized_keys, giving NETCONF access on TCP/830 as vmanage-admin (Rapid7, 2026-05-14). Rapid7 demonstrates the bypass with its own Metasploit module, submitted to the public Metasploit Framework repository (Rapid7, 2026-05-14). Cisco became aware of limited exploitation in May 2026 (Cisco PSIRT), and Talos attributes it to UAT-8616, a highly sophisticated actor that attempted to add SSH keys, modify NETCONF configurations and escalate to root (Cisco Talos, 2026-05-14). Talos separately tracks ten other clusters, distinct from UAT-8616, that exploit the earlier SD-WAN Manager flaws CVE-2026-20133, CVE-2026-20128 and CVE-2026-20122 with public proof-of-concept code (Cisco Talos, 2026-05-14). CISA added CVE-2026-20182 to its Known Exploited Vulnerabilities catalog on 2026-05-14 (CISA KEV catalog, 2026-05-14), under its existing Emergency Directive 26-03 for Cisco SD-WAN, first issued on 2026-02-25 (CISA ED 26-03).
Cisco lists no workaround; first fixed releases are 20.9.9.1, 20.12.5.4, 20.12.6.2 or 20.12.7.1, 20.15.4.4 or 20.15.5.2, 20.18.2.2 and 26.1.1.1, releases before 20.9 must migrate, and 20.10, 20.11, 20.13, 20.14 and 20.16 move to the next fixed train (Cisco PSIRT).
Cited evidence
In May 2026, the Cisco Product Security Incident Response Team (PSIRT) became aware of limited exploitation of this vulnerability.
Updates1
CISA's Emergency Directive 26-03 was first issued on 2026-02-25; on 2026-05-14 CISA added CVE-2026-20182 to its KEV catalog under it (CISA ED 26-03) (CISA KEV catalog, 2026-05-14). The SSH-key and NETCONF path Rapid7 demonstrated is on the SD-WAN Controller (Rapid7, 2026-05-14), and Cisco has since added the Validator to the affected products (Cisco PSIRT). Talos's ten other clusters exploit the separate SD-WAN Manager flaws CVE-2026-20133, CVE-2026-20128 and CVE-2026-20122, not this one (Cisco Talos, 2026-05-14). Cisco lists no workaround and no source proposes segmentation as one. Rapid7 demonstrates the bypass with its own Metasploit module, submitted to the public Metasploit Framework repository, so a working exploit is public (Rapid7, 2026-05-14).
Sources5
Revision history
- Published 2026-05-15-58b94fbd
- Correction 2026-10-11T1307Z-audit
CISA did not issue Emergency Directive 26-03 on 2026-05-14: the directive dates from 2026-02-25, and on 2026-05-14 CISA added the flaw to its KEV catalog under it. The NETCONF and SSH-key path Rapid7 demonstrated is on the Controller, not the Manager; Talos names exactly ten other clusters exploiting a separate set of February flaws; the segmentation mitigation had no source; and the flaw is an authentication bypass, not code execution. The entry is rewritten with the Validator added, Cisco's indicators and pre-upgrade evidence step, the UAT-8616 attribution, verbatim evidence, a rating, an ATT&CK mapping and a link to the separate CVE-2026-20245 entry. Rapid7's Metasploit module, submitted to the public framework repository, is now named, and the flaw's status gains poc-public.
Changed: title headline summary immediate_action tags entities techniques affected_products cves sources evidence sourcing_note references classification body
AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.