ForumsExploitsCisco SD-WAN CVE-2026-20182: CVSS 10 Auth Bypass - Patch ASAP

Cisco SD-WAN CVE-2026-20182: CVSS 10 Auth Bypass - Patch ASAP

MDR_Analyst_Chris 5/14/2026 USER

Just saw the advisory drop for CVE-2026-20182. It’s a max-severity authentication bypass in the peering authentication of the Cisco Catalyst SD-WAN Controller (formerly vSmart). With a CVSS score of 10.0 and confirmed active exploitation, this is the definition of 'drop everything and patch.'

The flaw allows an unauthenticated, remote attacker to bypass authentication and assume administrative privileges. If you have your management interfaces exposed to the internet, you are essentially inviting a full takeover of your WAN fabric.

I've started checking our version strings against the advisory. If you need to verify if you are vulnerable, you can check your software version:

show version | include "Release"

Regarding detection, since this is an auth bypass, standard logs might not show a failed login. We are looking for successful admin sessions originating from unusual IPs or configuration changes outside of change windows.

Here’s a quick KQL query for Sentinel/defender users to hunt for suspicious config pushes:

CiscoSDWANEvent
| where EventType == "Configuration"
| where initiating_user != "admin_user_1" and initiating_user != "admin_user_2"
| summarize count() by SrcIpAddr, initiating_user


Is anyone else pushing emergency patches tonight, or are you relying on WAF rules and IP whitelisting until the next maintenance window?
RE
RedTeam_Carlos5/14/2026

Patch immediately. We attempted to mitigate by restricting management access to VPN-only, but given the CVSS 10 rating, we couldn't risk it. The upgrade was smooth on the controllers, but don't forget the edge devices if they list shared components in the advisory.

TA
TabletopEx_Quinn5/14/2026

This is scary because of how critical SD-WAN is for connectivity. If the controller is popped, they can re-route traffic easily. We're checking our netflow data for any unexpected tunnel spikes. I recommend checking your configuration backups for any unauthorized changes made recently.

DN
DNS_Security_Rita5/14/2026

If you can't patch immediately, restrict management plane access strictly to internal subnets via ACLs. There is absolutely no excuse for having vSmart or the Controller exposed directly to the public internet in 2026.

Verified Access Required

To maintain the integrity of our intelligence feeds, only verified partners and security professionals can post replies.

Request Access

Thread Stats

Created5/14/2026
Last Active5/14/2026
Replies3
Views174