CVE-2026-20182: Critical authentication bypass in Cisco Catalyst SD-WAN Controller (FIXED)
Rapid7 Labs (Jonah Burgess, Stephen Fewer) discovered and analyzed CVE-2026-20182, an authentication bypass in Cisco Catalyst SD-WAN Controller's vdaemon service (DTLS over UDP 12346). The vulnerability exists in vbond_proc_challenge_ack(): the function implements device-type-specific certificate verification for vSmart (type 3), vManage (type 5), and vEdge (type 1), but has no code path for device_type==2 (vHub). A peer claiming to be a vHub in the CHALLENGE_ACK message skips all verification and falls through to peer->authenticated=true. The 12-byte vdaemon message header encodes device_type in the upper nibble of byte 1. Post-authentication, an attacker can inject an SSH public key into the vmanage-admin user's authorized_keys file via MSG_VMANAGE_TO_PEER (type 14) and access NETCONF over SSH on TCP port 830. Cisco Talos confirmed active in-the-wild exploitation by UAT-8616 as of May 14, 2026. Cisco released fixed software releases; no workarounds exist. The vulnerability is distinct from CVE-2026-20127 but affects the same service and was discovered during investigation of that prior vulnerability.
Research notes
- Root causeIn vbond_proc_challenge_ack(), the function implements device-type-specific certificate verification for vSmart (type 3), vManage (type 5), and vEdge (type 1), but has no code path for device_type == 2 (vHub). A peer claiming to be a vHub skips all verification and falls through to peer->authenticated = true.
- Technical detailThe vdaemon protocol handshake over DTLS (UDP 12346) accepts any client certificate during the DTLS handshake, then performs device-type-specific verification during CHALLENGE_ACK processing. The 12-byte message header encodes device_type in the upper nibble of byte 1, and claiming type 2 (vHub) bypasses all subsequent verification.
- ExploitationPost-authentication, an attacker can inject an SSH public key into the vmanage-admin user's authorized_keys file via MSG_VMANAGE_TO_PEER (message type 14) and access NETCONF over SSH on TCP port 830 to issue arbitrary configuration commands. Cisco Talos has observed active in-the-wild exploitation by UAT-8616, including SSH key addition, NETCONF modification, and root escalation attempts.