cbcvebase.
CVE-2026-20245
published 2026-06-04

CVE-2026-20245: A vulnerability in the CLI of Cisco Catalyst SD-WAN Controller, formerly SD-WAN vSmart, Cisco Catalyst SD-WAN Manager, formerly SD-WAN vManage, and Cisco…

PriorityP185high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
KEVITW
CISA Known Exploited Vulnerabilitydue 2026-06-23
Exploited in the wild
EPSS
25.32%
97.7th percentile
A vulnerability in the CLI of 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 authenticated, local attacker to execute arbitrary commands as root by supplying a crafted file to the affected system. This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by uploading a crafted file to the affected system. A successful exploit could allow the attacker to perform command injection attacks on an affected system and elevate their privileges as the root user. To exploit this vulnerability, the attacker must have netadmin privileges on the affected system. This would require valid credentials or exploitation of or . Cisco is not aware of successful exploitation by other methods. Cisco has observed limited cases where the exploitation of this bug resulted in a configuration change pushed to edge devices. Cisco recommends that customers upgrade to the fixed software that is documented in the that was published on May 14, 2026, and verify the configuration of the edge devices.

Affected

534 ranges· showing 25
VendorProductVersion rangeFixed in
ciscocatalyst_sd-wan_manager< 20.9.9.120.9.9.1
ciscocatalyst_sd-wan_manager
ciscocatalyst_sd-wan_manager>= 20.10 < 20.12.5.420.12.5.4
ciscocatalyst_sd-wan_manager>= 20.12.6 < 20.12.6.220.12.6.2
ciscocatalyst_sd-wan_manager>= 20.13 < 20.15.4.420.15.4.4
ciscocatalyst_sd-wan_manager>= 20.15.5 < 20.15.5.220.15.5.2
ciscocatalyst_sd-wan_manager>= 20.16 < 20.18.2.220.18.2.2
ciscocatalyst_sd-wan_manager>= 26.1 < 26.1.1.126.1.1.1
ciscocisco_catalyst_sd-wan_controller
ciscocisco_catalyst_sd-wan_controller
ciscocisco_catalyst_sd-wan_controller
ciscocisco_catalyst_sd-wan_controller
ciscocisco_catalyst_sd-wan_controller
ciscocisco_catalyst_sd-wan_controller
ciscocisco_catalyst_sd-wan_controller
ciscocisco_catalyst_sd-wan_controller
ciscocisco_catalyst_sd-wan_controller
ciscocisco_catalyst_sd-wan_controller
ciscocisco_catalyst_sd-wan_controller
ciscocisco_catalyst_sd-wan_controller
ciscocisco_catalyst_sd-wan_controller
ciscocisco_catalyst_sd-wan_controller
ciscocisco_catalyst_sd-wan_controller
ciscocisco_catalyst_sd-wan_controller
ciscocisco_catalyst_sd-wan_controller

Detection & IOCsextracted from sources · hover to see the quote

path/etc/passwd
path/etc/shadow
othertroot (rogue root user account)
  • Look for unauthorized SD-WAN peering connections on service provider infrastructure as an early indicator of compromise preceding CVE-2026-20245 exploitation.
  • Monitor the SD-WAN Manager CLI tenant-upload feature for malicious CSV file uploads, specifically files used to trigger command injection.
  • Check /etc/passwd and /etc/shadow for unexpected accounts, particularly a hidden account named 'troot' with root-level shell access.
  • Collect diagnostic data from SD-WAN devices and check for signs of unauthorized peering connections; also review edge device configurations for unauthorized changes pushed by a compromised controller.
  • Treat the vmanage-admin account as a high-value target; monitor for its use in web interface logins followed by bulk configuration extraction of edge devices, controllers, and SD-WAN templates.
  • ·Exploitation requires netadmin privileges on the affected system; attackers likely obtained initial access via authentication bypass zero-days CVE-2026-20127 or CVE-2026-20182, or via stolen certificates from a prior breach.
  • ·A second wave of intrusions in March 2026 targeted a device patched against CVE-2026-20127; Cisco confirmed CVE-2026-20182 was not used, suggesting stolen certificates from a prior breach may have been leveraged for re-entry.
  • ·Cisco observed limited cases where successful exploitation resulted in unauthorized configuration changes being pushed to edge devices across the SD-WAN fabric.
  • ·No workarounds are available; vendor fix is the only remediation. FCEB agencies must apply fixes or mitigations by June 23, 2026.

CVSS provenance

nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vulncheck7.8HIGH
cisa7.8HIGH
CVEs like this are exactly what “Exploited This Week” covers.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.