Skip to content
Server Security Center
KEVcritical10.0

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

Cisco Catalyst SD-WAN · listed in the CISA catalog of actively exploited vulnerabilities since 2026-05-14.

CVSS v3.1 (CVE record)
10.0
critical
EPSS (exploit probability, 30 days)
91%
higher than 99.8% of all CVEs
Added to CISA KEV
2026-05-14
US federal due date 2026-05-17
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2026-20182 explained

CVE-2026-20182 is an authentication bypass in the peering authentication of Cisco Catalyst SD-WAN Controller, Manager and Validator. An unauthenticated, remote attacker could obtain administrative privileges and manipulate configuration of the SD-WAN fabric. CISA lists it as known exploited, so affected deployments need urgent attention.

Impact

An unauthenticated attacker with network access can send crafted requests and log in to an affected Controller as an internal, high-privileged, non-root account. From there the attacker can reach NETCONF and change network configuration for the whole SD-WAN fabric. No user interaction is needed. CISA rates it automatable with total technical impact, and attackers are known to exploit it. Confidentiality, integrity and availability impacts are all high, with changed scope.

Who is affected

Cisco Catalyst SD-WAN Controller (formerly vSmart): the CVE record lists 129 versions in 23 groups, with first and last listed 17.2.4 and 20.16.1. Cisco Catalyst SD-WAN Manager (formerly vManage): listed versions in branches 17.2, 18.2, 18.3, 18.4, 18.4ES, 19.1, 19.2, 20.1 and more. The description also names Cisco Catalyst SD-WAN Validator (formerly vBond). The CVE record names no fixed version; check the Cisco advisory for fix information.

Written with AI from the data on this page and checked against it automatically.

Official description

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.

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 and CISA’s Hunt & Hardening Guidance for Cisco SD-WAN Devices. Adhere to the applicable BOD 22-01 guidance for cloud services or discontinue use of the product if mitigations are not available.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Cisco Catalyst SD-WAN Controller
    Affected
    • 129 listed versions in 23 groups (17.2.4 … 20.16.1)
    all 129 listed versions
    • 17.2: 17.2.4 … 17.2.10 (7 versions)
    • 18.2: 18.2.0
    • 18.3: 18.3.0 … 18.3.8 (8 versions)
    • 18.4: 18.4.0 … 18.4.303 (7 versions)
    • 19.0: 19.0.0, 19.0.1a
    • 19.1: 19.1.0
    • 19.2: 19.2.0 … 19.2.929 (11 versions)
    • 19.3: 19.3.0
    • 20.1: 20.1.1 … 20.1.12 (5 versions)
    • 20.3: 20.3.1 … 20.3.8 (13 versions)
    • 20.4: 20.4.1 … 20.4.2.3 (5 versions)
    • 20.5: 20.5.1
    • 20.6: 20.6.1 … 20.6.8 (15 versions)
    • 20.7: 20.7.1, 20.7.2
    • 20.8: 20.8.1
    • 20.9: 20.9.1 … 20.9.9.2 (17 versions)
    • 20.10: 20.10.1, 20.10.1.1
    • 20.11: 20.11.1, 20.11.1.1
    • 20.12: 20.12.1 … 20.12.7.2 (14 versions)
    • 20.13: 20.13.1
    • 20.14: 20.14.1
    • 20.15: 20.15.1 … 20.15.5.3 (11 versions)
    • 20.16: 20.16.1
    Fixed in
    not stated
  • Cisco Catalyst SD-WAN Manager
    Affected
    • 17.2: 17.2.5, 17.2.6, 17.2.8, 17.2.9
    • 18.2: 18.2.0
    • 18.3: 18.3.0 … 18.3.7 (7 versions)
    • 18.4: 18.4.0 … 18.4.303 (5 versions)
    • 18.4ES: 18.4.501_ES
    • 19.1: 19.1.0
    • 19.2: 19.2.0 … 19.2.929 (9 versions)
    • 20.1: 20.1.1 … 20.1.12 (5 versions)
    • 20.3: 20.3.2
    Fixed in
    not stated

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: sec.cloudapps.cisco.com/security/center/content/CiscoSecu…
  • CISA's deadline for US federal agencies: 2026-05-17 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Identify all Catalyst SD-WAN Controller, Manager and Validator instances and their versions.
  2. Follow the Cisco security advisory and upgrade to the fixed release it names for your branch.
  3. Use the advisory's Show Control Connections guidance to check for unexpected control connections.
  4. Follow CISA Emergency Directive 26-03 and CISA's Hunt & Hardening Guidance for Cisco SD-WAN Devices to assess exposure and look for compromise.
  5. Restrict network access to SD-WAN control and management interfaces to trusted sources only.
  6. Review NETCONF activity and fabric configuration changes for unauthorized modifications.

The CVE record names no fixed version, but the Cisco advisory provides fix information. Until you have applied it, follow CISA's required action: apply Emergency Directive 26-03 and the Hunt & Hardening Guidance, follow BOD 22-01 for cloud services, restrict exposure of SD-WAN components, and discontinue use of the product if mitigations are not available.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-287 Improper Authentication

Questions about CVE-2026-20182

Is CVE-2026-20182 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-05-14, with a US federal due date of 2026-05-17. Whether it is used in ransomware is unknown.
Is this the same as the SD-WAN vulnerability disclosed in February 2026?
No. Cisco states this is a new vulnerability in control connection handshaking, discovered and fixed after the February 2026 disclosure, with its own advisory.
What can an attacker do after exploiting it?
The attacker can log in to the Controller as an internal high-privileged, non-root account, access NETCONF, and manipulate network configuration for the SD-WAN fabric.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.