2026-05-15CRITICALexploitedA forged vHub peer can plant an SSH key on Cisco SD-WAN controllers without credentials; Talos ties exploitation to UAT-8616
UAT-8616
actor · actor:uat-8616
UAT-8616, Sophisticated actor exploiting Cisco SD-WAN infrastructure since 2023
Coverage
2
1 about it · 1 mention · first 2026-05-15 → last 2026-10-21
Latest activity
2026-05-15
A forged vHub peer can plant an SSH key on Cisco SD-WAN controllers without credentials; Talos ties…
Peak priority
critical
1 critical
Targets
·
no sector or region stated
Sources cited
9
6 hosts
2026-05-152 appearances2026-06-16
Action items (1)
Do-now tasks recorded on the entries about UAT-8616, newest first. Check the date before acting on an older one.
- 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 UAT-8616 tells a defender to do, newest first.
Exposure · detection
Story timeline
Every entry that names UAT-8616, newest first. Rows tagged mention only name it in passing: they are listed for completeness and add nothing to the action items, pivots or ATT&CK profile on this page.
- 2026-06-16CVE-2026-20262: Cisco Catalyst SD-WAN Manager authenticated arbitrary file write, exploited and KEV-listed; Cisco says a written file could later be used to gain root
- 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)
Affected products
ATT&CK techniques (3 across 4 tactics)
3 techniques observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)
- Initial AccessExploit Public-Facing Application
- PersistenceAccount Manipulation: SSH Authorized Keys
- Privilege EscalationAccount Manipulation: SSH Authorized Keys
- 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 ↗
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 ↗
Privilege Escalation TA0004
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 ↗
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 UAT-8616 (1)
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 Manager×2
- Cisco Catalyst SD-WAN Controller×1
- Cisco Catalyst SD-WAN Controller/Manager/Validator peering authentication bypass (CVSS 10.0), exploited by UAT-8616, CISA KEV 2026-05-14×1
- Cisco Catalyst SD-WAN Manager web UI authenticated path traversal, arbitrary file write to root RCE; CISA KEV 2026-06-15×1
- Cisco Catalyst SD-WAN Validator×1
Where this entity is cited
Source distribution
- sec.cloudapps.cisco.com3 (33%)
- cisa.gov2 (22%)
- bleepingcomputer.com1 (11%)
- blog.talosintelligence.com1 (11%)
- rapid7.com1 (11%)
- theregister.com1 (11%)
All cited sources (9)
- bleepingcomputer.comBleepingComputerhttps://www.bleepingcomputer.com/news/security/cisco-fixes-sd-wan-vmanage-flaw-exploited-in-zero-day-attacks/
- 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
- 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-arbfw-c2rZvQ
- 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
- theregister.comThe Registerhttps://www.theregister.com/patches/2026/06/15/cisco-sd-wan-make-me-root-bug-under-attack/5255916