## Summary
CVE-2026-20182 is a critical **authentication bypass** vulnerability affecting Cisco Catalyst SD-WAN Controller (formerly SD‑WAN vSmart) and Cisco Catalyst SD‑WAN Manager (formerly SD‑WAN vManage). An unauthenticated, remote attacker can exploit a flaw in the peering authentication mechanism to bypass authentication and obtain high-privileged administrative access to an affected system.
### Key details
– **Vulnerability type:** Authentication bypass (CWE-287)
– **Affected products:** Cisco Catalyst SD‑WAN Controller (vSmart) and Cisco Catalyst SD‑WAN Manager (vManage)
– **Attack vector:** Network (remote, unauthenticated)
– **CVSS v3.1:** 10.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) — **Critical**
– **Impact:** Confidentiality, Integrity, and Availability — **High**
### Technical impact
– The flaw stems from an issue in the **peering authentication mechanism** used by the SD‑WAN control plane.
– A successful exploit allows an attacker to log in to the SD‑WAN Controller/Manager as an internal, high‑privileged, non‑root user.
– With this access, an attacker can reach NETCONF interfaces and **manipulate SD‑WAN network configuration**, potentially causing network disruption, configuration rollback/poisoning, traffic interception, or broader lateral movement across the SD‑WAN fabric.
### Exploitation and activity
– Public reporting and vendor/telemetry sources indicate active exploitation/targeting is being tracked by security teams. Organizations should treat exposed management/control plane instances as high risk.
### Mitigation and recommendations
– **Apply vendor-provided patches immediately.** Cisco has published security advisories with remediation and guidance — consult the Cisco advisories linked below for fixed releases and step-by-step instructions.
– If immediate patching is not possible, implement compensating controls:
– Restrict network access to management/control plane interfaces (limit to trusted admin networks and management VPNs).
– Use strict ACLs and firewalling to block unauthenticated access to vManage/vSmart management endpoints.
– Monitor logs and NETCONF activity for unexpected configuration changes and anomalous authentication events.
– Follow the vendor guidance (including the “Show Control Connections” checks referenced in the advisory) to validate system state and connectivity.
## IONIX Status
The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.
References:

