CVE-2026-20182: Cisco Catalyst SD-WAN Controller Authentication Bypass Vulnerability

What it is

May 2026: This security advisory provides the details and fix information for a vulnerability that was discovered and fixed after the was disclosed in February 2026. This new advisory is for a new vulnerability in the control connection handshaking. The section of this advisory includes Show Control Connections guidance to help with system checks.  A vulnerability in the peering authentication in Cisco Catalyst SD-WAN Controller, formerly SD-WAN vSmart, Cisco Catalyst SD-WAN Manager, formerly SD-WAN vManage, and Cisco Catalyst SD-WAN Validator, formerly SD-WAN vBond, could allow an unauthenticated, remote attacker to bypass authentication and obtain administrative privileges on an affected system. This vulnerability exists because the peering authentication mechanism in an affected system is not working properly. An attacker could exploit this vulnerability by sending crafted requests to the affected system. A successful exploit could allow the attacker to log in to an affected Cisco Catalyst SD-WAN Controller as an internal, high-privileged, non-root user account. Using this account, the attacker could access NETCONF, which would then allow the attacker to manipulate network configuration for the SD-WAN fabric.

Exploitation evidence

First exploit evidence seen: 2026-05-07 (earliest date across the sources below).

Exploited in the wild

• CISA KEV: listed since 2026-05-14. Source

Public exploit code

Metasploit

• auxiliary/admin/networking/cisco_sdwan_vhub_auth_bypass: Cisco Catalyst SD-WAN Controller vHub Authentication Bypass (disclosure 2026-05-07)

GitHub proof-of-concept repositories

3 public repositories from 3 accounts, first seen 2026-05-22. Most starred: portbuster1337/CVE-2026-20182 (3 stars), view repository.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: CISA KEV · Rapid7 Metasploit Framework module metadata · nomi-sec/PoC-in-GitHub.

How to fix it

CISA required action

Please adhere to CISA’s guidelines to assess exposure and mitigate risks associated with Cisco SD-WAN devices as outlined in CISA’s Emergency Directive 26-03 (URL listed below in Notes) and CISA’s Hunt & Hardening Guidance for Cisco SD-WAN Devices (URL listed below in Notes). Adhere to the applicable BOD 22-01 guidance for cloud services or discontinue use of the product if mitigations are not available. (source: CISA KEV)

Fixed versions

• cisco catalyst sd-wan manager: upgrade to 20.9.9.1 or later
• cisco catalyst sd-wan manager: upgrade to 20.12.5.4 or later (affected from 20.10)
• cisco catalyst sd-wan manager: upgrade to 20.12.6.2 or later (affected from 20.12.6)
• cisco catalyst sd-wan manager: upgrade to 20.15.4.4 or later (affected from 20.13)
• cisco catalyst sd-wan manager: upgrade to 20.15.5.2 or later (affected from 20.15.5)
• cisco catalyst sd-wan manager: upgrade to 20.18.2.2 or later (affected from 20.16)
• cisco catalyst sd-wan manager: upgrade to 26.1.1.1 or later (affected from 26.1)
• cisco sd-wan vbond orchestrator: upgrade to 20.9.9.1 or later
• cisco sd-wan vbond orchestrator: upgrade to 20.12.5.4 or later (affected from 20.10)
• cisco sd-wan vbond orchestrator: upgrade to 20.12.6.2 or later (affected from 20.12.6)
• cisco sd-wan vbond orchestrator: upgrade to 20.15.4.4 or later (affected from 20.13)
• cisco sd-wan vbond orchestrator: upgrade to 20.15.5.2 or later (affected from 20.15.5)
• cisco sd-wan vbond orchestrator: upgrade to 20.18.2.2 or later (affected from 20.16)
• cisco sd-wan vbond orchestrator: upgrade to 26.1.1.1 or later (affected from 26.1)
• cisco sd-wan vsmart controller: upgrade to 20.9.9.1 or later
• cisco sd-wan vsmart controller: upgrade to 20.12.5.4 or later (affected from 20.10)
• cisco sd-wan vsmart controller: upgrade to 20.12.6.2 or later (affected from 20.12.6)
• cisco sd-wan vsmart controller: upgrade to 20.15.4.4 or later (affected from 20.13)
• cisco sd-wan vsmart controller: upgrade to 20.15.5.2 or later (affected from 20.15.5)
• cisco sd-wan vsmart controller: upgrade to 20.18.2.2 or later (affected from 20.16)
• cisco sd-wan vsmart controller: upgrade to 26.1.1.1 or later (affected from 26.1)

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

• https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-rpa2-v69WY2SW (CISA KEV notes)

MITRE ATT&CK mitigations for this chain

• M1048 Application Isolation and Sandboxing (for T1190) : Application isolation will limit what other processes and system features the exploited target can access.
• M1037 Filter Network Traffic (for T1190) : Restrict outbound network traffic from public-facing servers to prevent unauthorized connections from initiating communications with attacker-controlled infrastructure. While this may not prevent the initial exploitation, it limits the attacker's ability to verify and control the compromised server post-exploit, reduci
• M1030 Network Segmentation (for T1190) : Segment externally facing servers and services from the rest of the network with a DMZ or on separate hosting infrastructure.
• M1016 Vulnerability Scanning (for T1190) : Regularly scan externally facing systems for vulnerabilities and establish procedures to rapidly patch systems when critical vulnerabilities are discovered through scanning and through public disclosure.
• M1026 Privileged Account Management (for T1190, T1078) : Use least privilege for service accounts will limit what permissions the exploited process gets on the rest of the system.
• M1050 Exploit Protection (for T1190) : Web Application Firewalls may be used to limit exposure of applications to prevent exploit traffic from reaching the application.
• M1035 Limit Access to Resource Over Network (for T1190) : Ensure that all publicly exposed services are actually intended to be so, and restrict access to any that should only be available internally.
• M1051 Update Software (for T1190) : Update software regularly by employing patch management for externally exposed applications.
• M1027 Password Policies (for T1078) : Applications and appliances that utilize default username and password should be changed immediately after the installation, and before deployment to a production environment. When possible, applications that use SSH keys should be updated periodically and properly secured. Policies should minimize (if not eliminate)
• M1018 User Account Management (for T1078) : Regularly audit user accounts for activity and deactivate or remove any that are no longer needed.

Detection Generic guidance

• Initial Access: Alert on unusual requests to the affected service (odd paths, oversized payloads, exploit strings) in WAF, reverse-proxy and application logs.
• Persistence: Look for new files in web roots, new scheduled tasks/services, and new accounts created after the exposure window.
• Privilege Escalation: Alert on processes gaining SYSTEM/root unexpectedly, and on exploitation crashes of privileged services.

Response checklist Generic guidance

1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.