CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

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.

2026-05-15CRITICALexploitedA forged vHub peer can plant an SSH key on Cisco SD-WAN controllers without credentials; Talos ties exploitation to UAT-8616

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.

  1. 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
    mentiontrending-vulnerabilitiesAn SD-WAN Manager user with write access can overwrite any file; Cisco confirms limited exploitation
  2. 2026-05-15CVE-2026-20182: Cisco Catalyst SD-WAN peering authentication bypass (CVSS 10.0) exploited by UAT-8616; affects Controller, Manager and Validator
    trending-vulnerabilitiesA forged vHub peer can plant an SSH key on Cisco SD-WAN controllers without credentials; Talos ties exploitation to UAT-8616
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>&lt;user-home&gt;/.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>&lt;user-home&gt;/.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)

2026-05-15 · view entry permalink →

CRITICALCVE-2026-20182exploitedupdatedNATOA1

CVE-2026-20182: Cisco Catalyst SD-WAN peering authentication bypass (CVSS 10.0) exploited by UAT-8616; affects Controller, Manager and Validator

CVE-2026-20182 (CVSS 10.0, CWE-287) is an authentication bypass in the peering authentication of Cisco Catalyst SD-WAN Controller, Manager and, since Cisco's advisory revision of 2026-06-16, Validator, affecting all deployment types regardless of configuration (Cisco PSIRT). Rapid7 showed the mechanism on the Controller: the vdaemon DTLS control-plane service on UDP/12346 accepts a CHALLENGE_ACK claiming device type 2 (vHub) from a self-signed peer without verifying it, after which message type 14 (MSG_VMANAGE_TO_PEER) appends an attacker SSH key to /home/vmanage-admin/.ssh/authorized_keys, giving NETCONF access on TCP/830 as vmanage-admin (Rapid7, 2026-05-14). Rapid7 demonstrates the bypass with its own Metasploit module, submitted to the public Metasploit Framework repository (Rapid7, 2026-05-14). Cisco became aware of limited exploitation in May 2026 (Cisco PSIRT), and Talos attributes it to UAT-8616, a highly sophisticated actor that attempted to add SSH keys, modify NETCONF configurations and escalate to root (Cisco Talos, 2026-05-14). Talos separately tracks ten other clusters, distinct from UAT-8616, that exploit the earlier SD-WAN Manager flaws CVE-2026-20133, CVE-2026-20128 and CVE-2026-20122 with public proof-of-concept code (Cisco Talos, 2026-05-14). CISA added CVE-2026-20182 to its Known Exploited Vulnerabilities catalog on 2026-05-14 (CISA KEV catalog, 2026-05-14), under its existing Emergency Directive 26-03 for Cisco SD-WAN, first issued on 2026-02-25 (CISA ED 26-03).

Cisco lists no workaround; first fixed releases are 20.9.9.1, 20.12.5.4, 20.12.6.2 or 20.12.7.1, 20.15.4.4 or 20.15.5.2, 20.18.2.2 and 26.1.1.1, releases before 20.9 must migrate, and 20.10, 20.11, 20.13, 20.14 and 20.16 move to the next fixed train (Cisco PSIRT).

In May 2026, the Cisco Product Security Incident Response Team (PSIRT) became aware of limited exploitation of this vulnerability.

Cisco PSIRT
Correctionrun 2026-10-11T1307Z-audittitleheadlinesummaryimmediate_actiontagsentitiestechniquesaffected_productscvessourcesevidencesourcing_notereferencesclassificationbody

CISA's Emergency Directive 26-03 was first issued on 2026-02-25; on 2026-05-14 CISA added CVE-2026-20182 to its KEV catalog under it (CISA ED 26-03) (CISA KEV catalog, 2026-05-14). The SSH-key and NETCONF path Rapid7 demonstrated is on the SD-WAN Controller (Rapid7, 2026-05-14), and Cisco has since added the Validator to the affected products (Cisco PSIRT). Talos's ten other clusters exploit the separate SD-WAN Manager flaws CVE-2026-20133, CVE-2026-20128 and CVE-2026-20122, not this one (Cisco Talos, 2026-05-14). Cisco lists no workaround and no source proposes segmentation as one. Rapid7 demonstrates the bypass with its own Metasploit module, submitted to the public Metasploit Framework repository, so a working exploit is public (Rapid7, 2026-05-14).

Builds on: A netadmin user on Cisco SD-WAN can become root through a crafted upload file; Mandiant saw…

vulnerability15 May 05:00Zmulti-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns2

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)