Executive summary
On 28 October 2026 Cisco Talos published its analysis of KeyDrift, a malware framework it attributes to a cluster it tracks as UAT-11473, recovered from Cisco Catalyst SD-WAN control components reached through CVE-2026-20127 Talos. The report is explicitly historical: it reconstructs the implants from recovered samples and gives no intrusion dates, victim counts or dwell times. The vulnerability was disclosed on 25 February 2026, when Cisco published its advisory, the US Cybersecurity and Infrastructure Security Agency (CISA) issued Emergency Directive (ED) 26-03, and Talos attributed the exploitation it was then tracking to a different cluster, UAT-8616 Cisco, CISA, Talos, February. Cisco's 28 October advisory revision adds only the link to the new post Cisco.
What is new is the mechanism. KeyDrift's components are launched by trojanised runit service scripts and injected into vdaemon, the control-plane daemon, where they hook socket, Datagram Transport Layer Security (DTLS) and OpenSSL functions to take tasking in band and to copy what Talos assesses to be data-plane IPsec key material Talos. We assess it is likely (B2) that a controller carrying KeyDrift artefacts should be handled as a root-level compromise requiring the rebuild CISA's directive prescribes: the anchors sit in the root filesystem overlay and the implant's purpose is the fabric's keying material, so applying a fix alone does not establish that existing implants and compromised trust have been removed. On Volt Typhoon, Talos "assesses with high confidence that UAT-11473's operating infrastructure overlaps considerably with Volt Typhoon's 'Silent Train' covert access network" Talos. That is the whole of the reported relationship.
Chronology: disclosure clocks, not intrusion clocks
None of these dates is the date a KeyDrift implant was installed; Talos gives no such date.
| Date | Event | Source |
|---|---|---|
| 2023 | Earliest activity Talos found when investigating UAT-8616's exploitation of CVE-2026-20127; CISA's hunt guidance says activity "likely began in 2023" | Talos, February, CISA supplemental |
| Late 2025 | Lumen reports Volt Typhoon exploiting CVE-2026-20127 through Silent Train, continuing after the February disclosure; Lumen's attribution, naming neither UAT-11473 nor KeyDrift | Lumen |
| 25 February 2026 | Cisco advisory 1.0: Controller and Manager, no workaround, "limited exploitation", reported by the Australian Signals Directorate's Australian Cyber Security Centre (ASD's ACSC). CISA adds CVE-2026-20127 and CVE-2022-20775 to the Known Exploited Vulnerabilities (KEV) catalogue and issues ED 26-03 (patch by 27 February) with a joint alert; NCSC-UK publishes the co-sealed alert the same day. Talos publishes its UAT-8616 post. EUVD-2026-8675 is published | Cisco, CISA alert, ED 26-03, NCSC-UK, EUVD |
| 20 April and 14 May 2026 | CVE-2026-20133 and CVE-2026-20182 added to KEV: separate flaws, not part of the KeyDrift chain | CISA alert |
| 16 June 2026 | Advisory 2.0 adds the Validator (formerly vBond); EUVD record updated the same day | Cisco, EUVD |
| 28 October 2026 | Talos publishes the KeyDrift analysis; advisory 2.1 adds the link. Lumen's Silent Train report surfaces the same day (publication date verified in Lumen’s post-specific metadata) | Talos, Cisco |
| Not given | When UAT-11473 installed KeyDrift, for how long, against whom, and whether collected keys were used | Talos |
One register trap: the EUVD record's "exploited since" field reads 25 February 2026 EUVD, the disclosure date rather than the start of exploitation.
Two Talos clusters on one vulnerability
Three named clusters have been tied to CVE-2026-20127 and no source merges them: Talos's UAT-8616 and UAT-11473, and Volt Typhoon as reported by Lumen (next section). Talos's two attributions came eight months apart, without a stated relationship between them.
In February, Talos clustered the exploitation and post-compromise activity it was tracking as UAT-8616, assessed with high confidence to be a highly sophisticated actor. Partner investigation indicated the actor likely reached root by downgrading the controller software, exploiting CVE-2022-20775, a path-traversal flaw, and restoring the original version. The indicators were operational rather than malware-based, and no implant was named Talos, February.
In October, Talos described UAT-11473 as a highly sophisticated advanced persistent threat (APT) actor that exploited the same vulnerability and installed KeyDrift, with observed targeting in space and satellite services, defence and aerospace technology, and policy research Talos. The October post does not mention UAT-8616; the February post does not mention implants. We do not infer a link from the shared vulnerability: CISA describes actors compromising SD-WAN systems "globally" without naming any CISA alert, and a disclosed authentication bypass on an internet-reachable control plane is the kind of flaw more than one actor exploits.
| As reported by Talos | UAT-8616 (25 February) | UAT-11473 (28 October) |
|---|---|---|
| Entry | CVE-2026-20127 | CVE-2026-20127 |
| Escalation | Downgrade, CVE-2022-20775, version restored ("likely", partner finding) | Not described |
| Tooling | None named; account, SSH-key and log manipulation, unexplained peers, version changes with reboots | KeyDrift: PolyFlame, rsshd, conf_sshd, packed aaamgrd, LittleFilch |
| Earliest activity | 2023 | Not given; "historical" |
| Targeting | Not stated; Talos frames the activity within a trend of edge-device targeting of high-value and critical-infrastructure organisations | Space and satellite, defence and aerospace, policy research |
| Infrastructure | Not discussed | "Overlaps considerably" with Volt Typhoon's Silent Train network, high confidence |
Volt Typhoon: Talos's wording, and the linked report
Talos's Silent Train link goes to Lumen Black Lotus Labs' report, which describes the network as rapidly rotating chains of compromised small-office, Internet of Things and enterprise devices, exploited on demand, cleaned up after each operation and refreshed, observed consistently since November 2023. Lumen says that by late 2025 Volt Typhoon was exploiting Cisco Catalyst SD-WAN through CVE-2026-20127, targeting the trusted peering between SD-WAN devices and control infrastructure, and that exploitation continued well after Cisco's February disclosure Lumen. Lumen names neither UAT-11473 nor KeyDrift, and Talos does not say UAT-11473 is Volt Typhoon.
TIR assessment: an infrastructure overlap, however considerable, does not establish common control, and we keep the two as separate entries. Our companion profiles are UAT-11473 and Volt Typhoon; the 2023 Volt Typhoon profile remains in the archive.
How KeyDrift works
Entry, and the escalation Talos does not describe
A successful exploit lets an unauthenticated remote attacker log in to a Controller as an internal, high-privileged, non-root account and reach NETCONF, from which the fabric's configuration can be manipulated Cisco. From the fabric's side, the attacker-controlled rogue device appears as a new, temporary and legitimate SD-WAN component CISA supplemental.
KeyDrift's anchors need more than that account. Rewriting runit service directories under /etc/sv, remounting the /rootfs.rw overlay executable and injecting into vdaemon with ptrace are root-level actions; that is our reading, not a Talos statement. The October report does not say how UAT-11473 reached root. The downgrade route was reported for UAT-8616; whether UAT-11473 used it is unstated, so evidence of a downgrade, reboot or root session is relevant to a KeyDrift case even though the KeyDrift report does not mention it.
Execution anchor: trojanised runit services
In the sshd deployment, the service's run script keeps Cisco's startup logic but gains two lines: one remounts /rootfs.rw executable, the other backgrounds conf_sshd, which enumerates vdaemon process IDs, writes them to /tmp/system-vdaemon and calls the injector rsshd to inject PolyFlame (libdssl.so) into each process before the legitimate sshd starts Talos.
A second deployment masquerades as the aaamgr service: a malicious directory under /etc/sv/aaamgr/, a modified launcher and a binary named aaamgrd. The legitimate aaamgr is a Python package, not a compiled runit service. aaamgrd is a statically linked ELF64 with no section headers, a single read-write-execute segment and an RC4-encrypted embedded ELF payload; it uses direct system calls, reads TracerPid from /proc/<pid>/status and exits if a debugger is attached. Talos recovered this launcher from an affected Validator (vBond) appliance and saw timestomping with touch --reference= and chmod --reference= Talos. Talos's prose on the deletion of overlay PAM configurations for sshd and login is ambiguous about whether the step is legitimate, while its components table credits aaamgrd with tampering with PAM configurations; treat unexplained PAM changes as worth examining, not as confirmed either way.
PolyFlame: tasking from inside vdaemon
Injected into vdaemon, PolyFlame interposes recvfrom, sendto, getpeername, dlopen, dlsym and mprotect, parses /proc/<pid>/maps, and sees in-process state: DTLS session keys, vEdge topology, Overlay Management Protocol (OMP) routes and policy tables. No hardcoded addresses, ports, domains, URLs, host headers or polling interval were recovered; Talos concludes it is tasked in band over control-plane traffic rather than through a beacon Talos.
The hooked recvfrom calls the real function, learns the controller's address from the received data, and checks that the data carries the MD5 hash of the current date in %Y-%m-%d form; a mismatch stops execution. An administrative code then selects an action: 1 returns random bytes (a probable heartbeat), 2 sets backdoor or intermediate command-and-control (C2) mode, 3 initialises the intermediate-C2 handler, and other values route the payload to whichever mode is set. The backdoor mirrors TinyShell with different codes: 0x100 runs a command through /bin/sh -c, 0x200 writes a file, 0x300 reads one back; there is no interactive shell. The intermediate-C2 mode is a one-to-many relay: 0x403 opens and keeps a peer connection, 0x404 forwards data to it, 0x405 drops it, 0x407 returns a peer's response upstream, 0x408 sets a value in memory. Talos records the exact command format as unresolved Talos.
LittleFilch: key-material collection
LittleFilch (libcommon.so) hooks SSL_read inside vdaemon on an affected Controller (vSmart) process, calls the original function and inspects the decrypted buffer only when the length exceeds 0x18F bytes, the first byte is 0x07 and three markers are present Talos:
| Marker bytes | Field | Length | Talos's reading |
|---|---|---|---|
40 03 06 |
Public IP | 4 bytes | vEdge public or transport IP |
40 0C 04 |
Peer system IP | 4 bytes | vEdge OMP system IP |
05 01 0C 06 40 |
Binary key field | 32 bytes | Assessed OMP-distributed AES-256 IPsec data-plane key material |
The key-field identification is Talos's assessment, not a demonstrated decryption. LittleFilch RSA-encrypts each record to /var/tmp/vdaemon.bin and can send it over UDP in a DTLS 1.2 application-data-style record, to endpoints read from /var/tmp/vdaemon.conf, which it then deletes. Talos did not recover that file, so the destination is unknown Talos.
Placement and persistence limits
| Component | Where it lives | Persistence as reported, and what is not |
|---|---|---|
| PolyFlame, LittleFilch | vdaemon process memory | Lost when the process exits; re-established by the runit anchor at service start (our inference). Re-injection after a vdaemon restart alone is not described |
Trojanised run scripts, conf_sshd, rsshd, aaamgrd |
/etc/sv/sshd/, /etc/sv/aaamgr/ in the root overlay |
Mapped by Talos to T1037, implying reboot survival. Survival across an in-place upgrade is not stated; a fresh-image rebuild removes them by construction |
vdaemon.bin, vdaemon.conf |
/var/tmp |
Staging file, retention not described; the config file is deleted after reading, so its absence is expected |
Talos assesses with high confidence that the framework is designed to provide long-term persistent access and automated exfiltration of sensitive keying material, and reads the variation across modules and deployments as active development Talos. That is a statement of design intent. Observed persistence has a mechanism but no measured duration: no dwell time, first-seen date or victim count is given.
Affected components and fixed releases
Cisco's advisory, at version 2.1, says CVE-2026-20127 affects the Catalyst SD-WAN Controller (formerly vSmart), Manager (formerly vManage) and Validator (formerly vBond) regardless of configuration, across on-premises and Cisco-hosted deployments; the Validator was added on 16 June Cisco. ED 26-03's risk statement named the Manager and Controller, but its collection step already covers network logs for vManage, vSmart and vBond appliances and its root-compromise step requires fresh instances of all three ED 26-03. Validators belong in scope on both counts, and the packed aaamgrd loader is the component Talos recovered from one Talos.
| Release train | First fixed release (Cisco) |
|---|---|
| Earlier than 20.9 | Migrate to a fixed release |
| 20.9 | 20.9.8.2 |
| 20.11 (end of software maintenance) | 20.12.6.1 |
| 20.12 | 20.12.5.3 or 20.12.6.1 |
| 20.13 and 20.14 (end of software maintenance) | 20.15.4.2 |
| 20.15 | 20.15.4.2 |
| 20.16 (end of software maintenance) | 20.18.2.1 |
| 20.18 | 20.18.2.1 |
There is no workaround. As a temporary mitigation on premises, Cisco recommends restricting ports 22 and 830 to known controller and other known addresses; for hosted variants it says guardrails are in place. Cisco is aware of limited exploitation and lists Snort rules 65938 and 65958 for the vulnerability Cisco. Cisco's February remediation document, updated 19 March, provides upgrade images for Manager, Controller and Validator per fixed release and notes a separate fixed release, 20.15.405, for the Cisco-hosted cluster deployment. Its own version table differs from the advisory's: it maps 20.10 and 20.11 to 20.12.5.3 where the advisory maps 20.11 to 20.12.6.1, and it lists 20.3, 20.6 and 20.17 trains the advisory does not Cisco remediation. The advisory's table above is authoritative: Cisco says its PSIRT validates only the affected and fixed release information documented in the advisory Cisco.
The European Vulnerability Database record EUVD-2026-8675 carries CVE-2026-20127 and a GitHub advisory identifier as aliases, a CVSS 3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), Cisco as assigner and the Cisco advisory as reference. Other Cisco SD-WAN flaws of 2026, including CVE-2026-20133 and CVE-2026-20182 CISA alert and the authenticated CVE-2026-20245 in our earlier article, have separate advisories and are not part of the KeyDrift chain as Talos describes it.
Detection
Three layers, in different places. The first two are published guidance; the third is derived from Talos's description and is illustrative until tested.
Entry stage (Cisco and Talos, February). Audit /var/log/auth.log for Accepted publickey for vmanage-admin from addresses that are not configured system IPs, and manually validate every control-connection peering event, especially peer-type:vmanage, against maintenance windows, owned address ranges, documented system IPs and expected device roles Cisco, Talos, February.
Post-access (CISA hunt guidance). CISA's supplemental direction, which it says leverages ASD's ACSC's co-sealed Cisco SD-WAN Threat Hunt Guide, sets six checks: unexpected downgrades and reboots in the sw script logs under /var/volatile/log and /var/log/tmplog; upgrade-confirmation timeouts within 15 minutes of a downgrade; rogue peering (unusual peer types, outlier public IPs, null remote colours); SSH abuse through /home/vmanage-admin/.ssh/authorized_keys; root login anomalies, since root "should never be used interactively"; and log clearing, including zero-byte wtmp, lastlog and shell histories. Expect artefact removal: the actor cleared logs, histories and configurations and took steps to prevent log forwarding CISA supplemental. One documented false positive for the root check: Cisco says system-login-change notifications for user root are seen when admin-tech files are generated and during reboots, so a root entry that coincides with collection or a reboot is not by itself an anomaly Cisco remediation. CISA directs readers to the full guide for all of its detections and artefacts; the guide is published by ASD's ACSC and co-sealed by CISA, NSA and the Canadian, New Zealand and UK centres NCSC-UK, and could not be retrieved for this article, so its contents are not characterised here.
Two scoping facts from the February reporting apply to any SD-WAN compromise, including a KeyDrift case, although both describe the unnamed activity CISA investigated then, not UAT-11473. CISA's supplemental direction says international partners observed lateral movement outside the Cisco SD-WAN environment CISA supplemental. And the co-sealed alert says the cluster targeted organisations using Catalyst SD-WANs globally and that management interfaces exposed to the internet are at most risk NCSC-UK.
KeyDrift artefacts (derived from Talos).
| Artefact or behaviour | Where | Assumes | Limits |
|---|---|---|---|
Lines in /etc/sv/sshd/run that remount /rootfs.rw executable or background a script; /etc/sv/aaamgr/ with a compiled aaamgrd |
Root overlay, via admin tech dump or forensic snapshot | A known-good image of the same release; legitimate aaamgr is a Python package | Diff needs the matching image |
conf_sshd, rsshd, libdssl.so, libcommon.so, /tmp/system-vdaemon, /var/tmp/vdaemon.bin |
Filesystem, snapshot before reboot | Names from analysed samples; the actor timestomps and cleans up | Absence does not clear a host |
Unexpected shared objects in /proc/<pid>/maps of vdaemon |
Live controller | A baseline of expected libraries | Version drift; a lead, not proof |
| UDP from a controller to a non-fabric address resembling DTLS application data | Firewall, NetFlow or capture at the controller edge | Egress telemetry and an enumerable peer list | Legitimate DTLS to edges and Manager; destination unknown, so a hunt, not a rule |
Talos's network coverage for the artefacts is Snort 2 rules 67387 to 67416 and Snort 3 rules 7:44 to 7:73 Talos. Because PolyFlame is tasked inside existing control-plane traffic and LittleFilch uses a DTLS-style record to an unrecovered destination, host artefacts, not network rules, are the primary evidence.
Response and recovery
Steps 1 to 5 restate published requirements and vendor guidance, with the sources named; anything marked "TIR" in them, and steps 6 and 7 in full, are our inference from the mechanism. Cisco's remediation document and CISA's directive agree on collecting evidence before changing state; they differ on what follows, and the sequence below keeps both visible rather than merging them.
- Inventory every Controller, Manager and Validator, including hosted instances, and collect before changing state: an admin tech dump including parts of
/optand/var, a copy of/home, external syslogs and, on premises, a forensic snapshot and network logs for the vManage, vSmart and vBond appliances; cloud customers request snapshots and traffic logs from Cisco ED 26-03. Cisco asks for admin-tech from every control component, Controllers one at a time Cisco remediation. - Open a Cisco Technical Assistance Center (TAC) case and upload the admin-tech bundles. Cisco's ordering is TAC-first: it says not to start the upgrade before TAC has analysed the admin-tech files, and that an upgrade must remain within the current major release unless TAC directs otherwise Cisco remediation. ED 26-03 set federal agencies a different clock: collect first, then apply updates by 27 February ED 26-03. Where a deadline forces an upgrade before TAC reports, the evidence collected in step 1 is what preserves the assessment; this reading of the two documents is TIR's.
- Update for both vulnerabilities the directive names. ED 26-03 requires Cisco's updates for all of the CVEs it identifies, CVE-2026-20127 and CVE-2022-20775, and references Cisco advisory cisco-sa-sdwan-authbp-qwCX8D4v for the latter ED 26-03; the joint alert describes escalation through CVE-2022-20775 in the February activity CISA alert. Whether UAT-11473 used that flaw is not reported, but its fix status for the trains in use must be checked against that advisory. For CVE-2026-20127, upgrade within the current major release to the first fixed release in the advisory's table, restricting ports 22 and 830 meanwhile Cisco.
- Hunt with the CISA steps and the KeyDrift artefacts. TIR recommendation, not a directive requirement: given the lateral movement CISA's partners reported, scope beyond the control components to the hosts and the VPN 512 management networks those components can reach; CISA's hardening guidance places VPN 512 interfaces on an isolated management VLAN, which is hardening rather than a hunt instruction CISA supplemental.
- Where root compromise is found, CISA requires fresh Manager, Controller and Validator instances from patched images, edges migrated to them and new administrator accounts with unique credentials CISA supplemental. Cisco routes a TAC finding of indicators of compromise to PSIRT-guided remediation and a clean finding to an in-train upgrade Cisco remediation. TIR threshold: a KeyDrift anchor in the root overlay is evidence of root-level control, so we apply the rebuild requirement to any confirmed artefact.
- Treat the fabric's keying material as exposed: LittleFilch's target is assessed IPsec data-plane key material and PolyFlame sees DTLS session keys. After the rebuild, re-establish control connections and rotate what the old controllers held, on the TAC-guided path. CISA's hardening prefers pairwise keys between controllers and edges over the default exchange in which the Controller sends IPsec keys to each edge CISA supplemental; Talos does not say whether that would have denied LittleFilch usable material, so adopt it as hardening, not as a retrospective answer.
- Keep logs off the appliance and alert from the external collector on
peer-type:vmanageorpeer-type:vsmartwithnew-state:upand on any successful root authentication CISA supplemental. External collection survives on-box clearing only while forwarding is intact, and CISA reports the actor took steps to prevent forwarding, so alert on gaps in the forwarding stream as well.
Open questions
- When UAT-11473 deployed KeyDrift, for how long and against how many organisations. The 2023 start belongs to the UAT-8616 investigation and CISA's hunt scoping; Lumen's "late 2025" is its own Volt Typhoon attribution. Neither is a KeyDrift date.
- How UAT-11473 reached root from the non-root account the vulnerability provides.
- Whether UAT-8616 and UAT-11473 are related. Talos has published nothing either way.
- Whether the lateral movement CISA's partners observed in the February activity has any counterpart in a KeyDrift intrusion; Talos describes none, and ASD's full hunt guide could not be checked.
- PolyFlame's upstream controller and in-band command format; LittleFilch's destination.
- Whether collected key material was used against fabric traffic. Talos describes capability and assessed intent, not use.
- Whether KeyDrift survives an in-place software upgrade, as distinct from a rebuild.
Related TIR coverage
UAT-11473 and Volt Typhoon companion profiles; the 2023 Volt Typhoon profile; CVE-2026-20245 on Catalyst SD-WAN Manager, a separate flaw; and FIRESTARTER on Cisco firewalls, the same patching-versus-eviction distinction. None of these links asserts common attribution.
Sources
- Cisco Talos, Inside KeyDrift, 28 October 2026; Active exploitation of Cisco Catalyst SD-WAN by UAT-8616, 25 February 2026.
- Cisco, advisory cisco-sa-sdwan-rpa-EHchtZk, version 2.1, 28 October 2026; Remediate Catalyst SD-WAN Security Advisory, February 2026, updated 19 March 2026.
- CISA, ED 26-03, 25 February 2026, updated 11 March; Supplemental Direction, 25 February; joint alert, 25 February, revised 14 May 2026.
- NCSC-UK, Exploitation of Cisco Catalyst SD-WAN, 25 February 2026, updated 3 March 2026.
- Lumen Black Lotus Labs, Silent Train, 28 October 2026; post-specific publication metadata verified.
- ENISA, EUVD-2026-8675, published 25 February 2026, updated 16 June 2026.