2026-06-06HIGHexploitedAn attacker with netadmin access on Cisco SD-WAN can become root through a crafted tenant file; Mandiant saw it used as a zero-day in April
Cisco Catalyst SD-WAN Validator
product · product:cisco-catalyst-sd-wan-validator
Coverage
2
first 2026-05-15 → last 2026-10-11
Latest activity
2026-06-27
An attacker with netadmin access on Cisco SD-WAN can become root through a crafted tenant file; Mandiant saw…
Peak priority
critical
1 critical · 1 high
Targets
·
regions: switzerland
Sources cited
8
6 hosts
Action items (2)
Do-now tasks recorded on the entries about Cisco Catalyst SD-WAN Validator, newest first. Check the date before acting on an older one.
- Upgrade every Catalyst SD-WAN Controller, Manager and Validator to its first fixed release (20.9.9.2, 20.12.7.2, 20.15.4.5 or 20.15.5.3, 20.18.3.1 or 26.1.1.2) after retaining logs, then check /etc/passwd and /etc/shadow for unexpected UID-0 accounts.2026-06-06CVE-2026-20245 +2
- Immediate action: Run request admin-tech on every control component, then upgrade to a fixed release (for example 20.9.9.1, 20.12.7.1, 20.15.5.2, 20.18.2.2 or 26.1.1.1); check auth.log and control-connection history for the documented indicators, because on a compromised system the upgrade alone does not remediate.2026-05-15CVE-2026-20182
Defender insights
What each entry about Cisco Catalyst SD-WAN Validator tells a defender to do, newest first.
Exposure · detection
Exposure · detection
Story timeline
- 2026-06-06CVE-2026-20245: Cisco Catalyst SD-WAN netadmin-to-root command injection exploited as a zero-day; fixed releases and a Live Protect shield available
- 2026-05-15CVE-2026-20182: Cisco Catalyst SD-WAN peering authentication bypass (CVSS 10.0) exploited by UAT-8616; affects Controller, Manager and Validator
Hunting pivots
CVEs (exploited first)
Releases covered
Cisco Catalyst SD-WAN Validator ×2
ATT&CK techniques (7 across 6 tactics)
7 techniques observed across 2 entries about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v19.2 · compare on the matrix · Navigator layer (JSON)
- Initial AccessExploit Public-Facing Application
- ExecutionCommand and Scripting Interpreter: Unix Shell
- PersistenceAccount Manipulation: SSH Authorized Keys · Create Account: Local Account
- Privilege EscalationExploitation for Privilege Escalation · Account Manipulation: SSH Authorized Keys
- StealthIndicator Removal: File Deletion
- Lateral MovementRemote Services: SSH
Initial Access TA0001
T1190Exploit Public-Facing Application×1
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.
Evidence: 2026-05-15/cve-2026-20182-cisco-catalyst-sd-wan-controller-manager-pre · ATT&CK page ↗
Execution TA0002
T1059.004Command and Scripting Interpreter: Unix Shell×1
Adversaries may abuse Unix shell commands and scripts for execution. Unix shells are the primary command prompt on Linux, macOS, and ESXi systems, though many variations of the Unix shell exist (e.g. sh, ash, bash, zsh, etc.) depending on the specific OS or distribution. Unix shells can control every aspect of a system, with certain commands requiring elevated privileges.
Evidence: 2026-06-06/cve-2026-20245-cisco-catalyst-sd-wan-manager-actively-exploi · ATT&CK page ↗
Persistence TA0003
T1098.004Account Manipulation: SSH Authorized Keys×1
Adversaries may modify the SSH <code>authorized_keys</code> file to maintain persistence on a victim host. Linux distributions, macOS, and ESXi hypervisors commonly use key-based authentication to secure the authentication process of SSH sessions for remote management. The <code>authorized_keys</code> file in SSH specifies the SSH keys that can be used for logging into the user account for which the file is configured. This file is usually found in the user's home directory under <code><user-home>/.ssh/authorized_keys</code> (or, on ESXi, `/etc/ssh/keys-<username>/authorized_keys`). Users may edit the system’s SSH config file to modify the directives `PubkeyAuthentication` and `RSAAuthentication` to the value `yes` to ensure public key and RSA authentication are enabled, as well as modify the directive `PermitRootLogin` to the value `yes` to enable root authentication via SSH. The SSH config file is usually located under <code>/etc/ssh/sshd_config</code>.
Evidence: 2026-05-15/cve-2026-20182-cisco-catalyst-sd-wan-controller-manager-pre · ATT&CK page ↗
T1136.001Create Account: Local Account×1
Adversaries may create a local account to maintain access to victim systems. Local accounts are those configured by an organization for use by users, remote support, services, or for administration on a single system or service.
Evidence: 2026-06-06/cve-2026-20245-cisco-catalyst-sd-wan-manager-actively-exploi · ATT&CK page ↗
Privilege Escalation TA0004
T1068Exploitation for Privilege Escalation×1
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Security constructs such as permission levels will often hinder access to information and use of certain techniques, so adversaries will likely need to perform privilege escalation to include use of software exploitation to circumvent those restrictions.
Evidence: 2026-06-06/cve-2026-20245-cisco-catalyst-sd-wan-manager-actively-exploi · ATT&CK page ↗
T1098.004Account Manipulation: SSH Authorized Keys×1
Adversaries may modify the SSH <code>authorized_keys</code> file to maintain persistence on a victim host. Linux distributions, macOS, and ESXi hypervisors commonly use key-based authentication to secure the authentication process of SSH sessions for remote management. The <code>authorized_keys</code> file in SSH specifies the SSH keys that can be used for logging into the user account for which the file is configured. This file is usually found in the user's home directory under <code><user-home>/.ssh/authorized_keys</code> (or, on ESXi, `/etc/ssh/keys-<username>/authorized_keys`). Users may edit the system’s SSH config file to modify the directives `PubkeyAuthentication` and `RSAAuthentication` to the value `yes` to ensure public key and RSA authentication are enabled, as well as modify the directive `PermitRootLogin` to the value `yes` to enable root authentication via SSH. The SSH config file is usually located under <code>/etc/ssh/sshd_config</code>.
Evidence: 2026-05-15/cve-2026-20182-cisco-catalyst-sd-wan-controller-manager-pre · ATT&CK page ↗
Stealth TA0005
T1070.004Indicator Removal: File Deletion×1
Adversaries may delete files left behind by the actions of their intrusion activity. Malware, tools, or other non-native files dropped or created on a system by an adversary (ex: Ingress Tool Transfer) may leave traces to indicate to what was done within a network and how. Removal of these files can occur during an intrusion, or as part of a post-intrusion process to minimize the adversary's footprint.
Evidence: 2026-06-06/cve-2026-20245-cisco-catalyst-sd-wan-manager-actively-exploi · ATT&CK page ↗
Lateral Movement TA0008
T1021.004Remote Services: SSH×1
Adversaries may use Valid Accounts to log into remote machines using Secure Shell (SSH). The adversary may then perform actions as the logged-on user.
Evidence: 2026-05-15/cve-2026-20182-cisco-catalyst-sd-wan-controller-manager-pre · ATT&CK page ↗
Entries about Cisco Catalyst SD-WAN Validator (2)
Co-occurring entities
Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.
- Cisco Catalyst SD-WAN Controller×2
- Cisco Catalyst SD-WAN Controller/Manager/Validator peering authentication bypass (CVSS 10.0), exploited by UAT-8616, CISA KEV 2026-05-14×2
- Cisco Catalyst SD-WAN Manager×2
- Cisco Catalyst SD-WAN Manager command-injection to root; Mandiant confirms pre-disclosure zero-day exploitation; patched (chains CVE-2026-20127/-20182)×1
- Cisco Catalyst SD-WAN Manager pre-auth RCE (UAT-8616 prior exploitation, Feb 2026)×1
- UAT-8616×1
Where this entity is cited
Source distribution
- cisa.gov2 (25%)
- sec.cloudapps.cisco.com2 (25%)
- blog.talosintelligence.com1 (12%)
- cloud.google.com1 (12%)
- rapid7.com1 (12%)
- security-hub.ncsc.admin.ch1 (12%)
All cited sources (8)
- blog.talosintelligence.comCisco Taloshttps://blog.talosintelligence.com/sd-wan-ongoing-exploitation/
- cisa.govCISA ED 26-03https://www.cisa.gov/news-events/directives/ed-26-03-mitigate-vulnerabilities-cisco-sd-wan-systems
- cisa.govCISA KEV cataloghttps://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json
- cloud.google.comMandianthttps://cloud.google.com/blog/topics/threat-intelligence/zero-day-exploitation-cisco-catalyst-sd-wan-manager
- rapid7.comRapid7https://www.rapid7.com/blog/post/ve-cve-2026-20182-critical-authentication-bypass-cisco-catalyst-sd-wan-controller-fixed/
- sec.cloudapps.cisco.comCisco PSIRThttps://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-privesc-4uxFrdzx
- sec.cloudapps.cisco.comCisco PSIRThttps://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-rpa2-v69WY2SW
- security-hub.ncsc.admin.chNCSC-CHhttps://security-hub.ncsc.admin.ch/#/posts/12579