Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-20182: Authentication Bypass in Cisco Catalyst SD-WAN Peering Authentication

Published May 14, 2026 · Updated 19 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 2 in a dayToday
CVSS10.0Critical · v3.1
EPSS91.1%100th percentile
CISA KEVYesAdded May 14, 2026
In the wildActivePer CISA KEV
Vendor
Cisco Systems
IdentifiersCVE-2026-20182CWE-287 · Improper Authentication

CVE-2026-20182 is an improper-authentication vulnerability in the peering-authentication mechanism of Cisco Catalyst SD-WAN Controller (formerly vSmart), SD-WAN Manager (formerly vManage), and SD-WAN Validator (formerly vBond). The peering authentication mechanism does not function correctly during control-connection handshaking. An unauthenticated remote attacker can send crafted requests to bypass authentication and authenticate to an affected SD-WAN Controller as an internal, high-privileged non-root account. The account can access NETCONF and manipulate SD-WAN fabric network configuration.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation grants an unauthenticated remote attacker administrative privileges and NETCONF access. The attacker can manipulate SD-WAN fabric network configurations, potentially disrupting network operations. Cisco reported limited, targeted exploitation of the vulnerability.

Mitigation

If you can’t patch tonight, do this now.

Before upgrading, collect diagnostic data with the request admin-tech command from each SD-WAN control component to preserve potential compromise evidence. Audit authentication logs for unauthorized source addresses and investigate affected systems for signs of compromise. Updates should be prioritized after appropriate testing.

Remediation

Patch, then assume compromise.

Apply the relevant Cisco security updates immediately. Migrate unsupported releases earlier than 20.9 to a fixed release. Fixed releases identified for affected trains include 20.9.9.1, 20.12.7.1, 20.12.5.4, 20.12.6.2, 20.15.4.4, 20.15.5.2, 20.18.2.2, and 26.1.1.1. Replace end-of-life releases 20.11, 20.13, 20.14, and 20.16.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
CVE-2026-20182This repository is a small standalone exploit repo with 2 files: a README describing CVE-2026-20182 and one Python exploit script, cve-2026-20182.py. It is not tied to a major exploit framework. The Python script is the clear entry point and implements an end-to-end network exploit against Cisco Catalyst SD-WAN Controller/Manager systems. The exploit targets the vdaemon DTLS service on UDP/12346. It uses the local openssl CLI as a DTLS transport helper rather than implementing DTLS directly in Python. After the DTLS session is established, the script parses the first received vdaemon message and expects a CHALLENGE (type 8). It then sends a crafted CHALLENGE_ACK using device_type=2 (vHub), exploiting the vulnerable authentication logic described in the README: the vHub code path lacks certificate verification and causes the peer to be marked authenticated. The script checks for a CHALLENGE_ACK_ACK (type 10) as a success indicator, sends a HELLO (type 5) to move the peer into UP state, and finally sends a MSG_VMANAGE_TO_PEER (type 14) containing an attacker-controlled SSH public key. Operationally, the script supports two modes for the SSH key material: it can read an existing public key from a user-supplied file, or it can generate a fresh 2048-bit RSA keypair using the Python cryptography library. When generating a keypair, it stores the private key locally at /tmp/cve-2026-20182_key with mode 0600. The intended post-exploitation effect is persistence and remote access as the vmanage-admin user, with the README explicitly stating that the key is injected into /home/vmanage-admin/.ssh/authorized_keys. The script can optionally verify success by opening an SSH-based NETCONF session to TCP/830 and sending a NETCONF <hello> message. The README also documents ordinary SSH access on TCP/22. Overall, this is a real exploit rather than a detector. Its main capability is unauthenticated network compromise of vulnerable Cisco SD-WAN control infrastructure by abusing a protocol-level authentication bypass and converting that access into SSH/NETCONF access via key injection. The code is concise and functional, with hardcoded protocol constants and a fixed post-exploitation action, making it best classified as OPERATIONAL rather than fully weaponized.portbuster1337 · Disclosed May 22, 2026 · markdown · python · networkOperationalCVE-2026-20182This repository contains two Python exploit implementations for CVE-2026-20182, an authentication bypass affecting Cisco Catalyst SD-WAN Controller/Manager vdaemon peering on UDP/12346. The repository structure is small: a top-level README and license, one standalone PoC at the root (cve-2026-20182-poc.py), and a more complete subdirectory CVE-2026-20182-portbuster1337 containing its own README and a second exploit script. The more credible and technically coherent exploit is CVE-2026-20182-portbuster1337/cve-2026-20182.py. It uses openssl s_client with DTLS 1.2 to connect to the target vdaemon service, waits for a CHALLENGE message, sends a crafted CHALLENGE_ACK claiming device_type=2 (vHub), checks for CHALLENGE_ACK_ACK as evidence of successful bypass, sends HELLO to move the peer into UP state, and then sends a MSG_VMANAGE_TO_PEER message containing an SSH public key buffer. If no key is supplied, it generates an RSA keypair locally and stores the private key at /tmp/cve-2026-20182_key. It can optionally verify post-exploitation access by opening an SSH-based NETCONF session to TCP/830 as vmanage-admin. This script is operational and aligned with the vulnerability description in the included documentation. The root-level cve-2026-20182-poc.py is also an exploit attempt, but it is less faithful to the documented protocol. It generates an SSH keypair, starts a local reverse-shell listener, creates a random AES key, sends an encrypted UDP payload intended to represent the vHub bypass, and then sends a second encrypted payload containing shell commands to append the SSH key to /home/vmanage-admin/.ssh/authorized_keys and launch a bash reverse shell to the attacker. It exposes attacker-controlled listener settings (default 0.0.0.0:4444). However, because the script invents its own AES-CBC wrapping without any demonstrated protocol negotiation or key exchange, it appears less reliable than the subdirectory exploit. Overall purpose: demonstrate exploitation of CVE-2026-20182 to gain unauthorized authenticated peer status in Cisco SD-WAN, then leverage that access for persistence and remote administration via injected SSH credentials; one variant additionally attempts interactive shell access via reverse shell. The repository is not part of a known exploit framework.HORKimhab · Disclosed May 24, 2026 · python · markdown · network · webOperationalCVE-2026-20182Repository contains a single substantial Python exploit script, CVE-2026-20182.py, plus README, license, and dependency file. The script is a standalone operational exploit/assessment tool targeting CVE-2026-20182 in Cisco Catalyst SD-WAN Controller/Manager peering authentication. It is not part of a common exploit framework. Core capability: the script performs a custom DTLS-based control-plane handshake against Cisco SD-WAN vdaemon, targeting UDP/12346 by default. It receives a CHALLENGE, sends a crafted CHALLENGE_ACK while impersonating a vHub device type, and attempts to complete the Hello exchange to validate authentication bypass. In full mode, it escalates from bypass validation to exploitation by generating SSH keys, sending a VMANAGE_TO_PEER message to inject a public key, expecting REGISTER_TO_VMANAGE as protocol acknowledgment, and then verifying access as vmanage-admin over TCP/830 NETCONF and optionally TCP/22 SSH. The exploit supports multithreaded scanning, target parsing/merging, fallback domain/site presets ((1,100), (1,1), (0,0)), optional extra UDP ports, and live telemetry. Output is structured into tiered result files: confirmed SSH compromise, injection acknowledged only, and bypass only. Local artifacts include JSONL result files, a summary JSON, a commands text file, and generated private keys under sdwan_keys/. Based on the README and visible code constants, this is more than a detector: it contains exploitation logic and a usable payload path (SSH key injection and login verification). The likely operator workflow is to run check mode for broad screening, then full mode on shortlisted hosts to obtain confirmed authenticated access.Nxploited · Disclosed May 26, 2026 · python · markdown · networkOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Cisco SystemsCatalyst SD-WAN Managerapplication
Cisco SystemsSd-Wan Vbond Orchestratorapplication
Cisco SystemsSd-Wan Vsmart Controllerapplication
FAQ

Frequently asked questions

Is CVE-2026-20182 exploited in the wild?
Yes. As of Oct 29, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on May 14, 2026.
Is there a public exploit for CVE-2026-20182?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2026-20182, the earliest disclosed May 22, 2026.
Is there a patch for CVE-2026-20182?
Apply the relevant Cisco security updates immediately. Migrate unsupported releases earlier than 20.9 to a fixed release.
What products are affected by CVE-2026-20182?
Cisco Systems Catalyst SD-WAN Manager, Cisco Systems Sd-Wan Vbond Orchestrator, and Cisco Systems Sd-Wan Vsmart Controller.
How severe is CVE-2026-20182?
CVE-2026-20182 has a CVSS v3.1 score of 10.0 (Critical) and an EPSS score of 91.1% (100th percentile) as of Oct 29, 2026.
Activity feed

Recent activity

268 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+46 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence17Every report linking this CVE to a named adversary.
Associated malware7Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity146Community discussion across Reddit, Mastodon, and other social sources.