Skip to main content
Emerging ThreatsMalware & Ransomware

Cisco SD-WAN Flaw Exploited to Deploy KeyDrift Malware

Network device on a rack with cables and patch panels, under fluorescent lighting with a blurred office space in the…

"Talos assesses with high confidence that the framework is designed to provide long-term persistent access and automated exfiltration of sensitive keying material," explained Cisco Talos.

CVE-2026-20127: the flaw and its exploit

CVE-2026-20127 is a maximum-severity authentication-bypass vulnerability in Cisco Catalyst SD-WAN Controllers that Cisco patched in February 2026. The flaw allows remote attackers to gain privileged access to Catalyst SD-WAN Controller and Manager instances and to add rogue peers. Cisco Talos researchers observed a threat cluster tracked as UAT-11473 exploiting that vulnerability to deploy a custom malware framework named KeyDrift. Earlier activity shows UAT-8616 exploited the same vulnerability as a zero-day since at least 2023, and recent research linked exploitation of the bug to the Chinese Volt Typhoon state-sponsored group; Talos said UAT-11473 appears to overlap with Volt Typhoon’s "Silent Train" covert access network but made no definitive attribution.

KeyDrift: goals and capabilities

According to Cisco Talos, KeyDrift is a bespoke malware framework designed to run on Cisco SD-WAN controller instances and to operate inside SD-WAN control-plane processes. Talos assessed with high confidence that KeyDrift is intended to maintain persistent access, intercept decrypted control traffic, extract control-session metadata and data-plane keying material, and stage or transmit the stolen material using encrypted records. The framework’s design centers on long-term presence and automated exfiltration of cryptographic key material for targeted edge nodes.

PolyFlame and LittleFilch: how the components work

Talos identified two main components of KeyDrift — PolyFlame and LittleFilch — and observed signs of ongoing development, including new anti-debugging features and varied process-impersonation techniques. PolyFlame executes inside legitimate vdaemon processes by using modified service startup scripts and an injector for deployment. It provides an attacker-facing TinyShell-styled command execution capability, supports file uploads and downloads, and can relay communications between an attacker’s command-and-control (C2) server and multiple peers.

LittleFilch is a control-session interception module that hooks SSL_read to inspect control-plane messages after they have been decrypted inside the controller. For predefined edge nodes, Talos observed LittleFilch extracting IP identifiers and a 32-byte field that Talos assesses to be AES-256 IPsec data‑plane key material. LittleFilch protects the collected information with RSA, saves it to /var/tmp/vdaemon.bin, and then transmits the data over UDP to the attacker infrastructure.

Targets, recommendations, and operational concern

Cisco Talos observed attacks using KeyDrift against organizations in space and satellite services, defense and aerospace technology, and policy research. Cisco’s public guidance is direct: system administrators should apply the available security updates for CVE-2026-20127 and consult the vendor’s dedicated hardening guide for Catalyst SD-WAN deployments. Talos’ technical characterization underscores a particular operational risk — because KeyDrift operates within control‑plane processes and can extract keying material, compromise can erode cryptographic protections that defend data-plane traffic.

The reporting also highlights a practical detection problem Cisco noted succinctly: "Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply." In other words, traditional prevention metrics may not reflect what attackers can do once they gain privileged controller access and run code inside the control plane.

What this means for space and satellite services, defense and aerospace technology, and policy research organizations

  • Space and satellite services: prioritize patching Catalyst SD-WAN Controllers and monitor SD-WAN control-plane processes for unauthorized vdaemon modifications; KeyDrift’s LittleFilch component writes to /var/tmp/vdaemon.bin and sends data over UDP, which defenders can use as an investigative signal.
  • Defense and aerospace technology organizations: treat exfiltration of IPsec key material as a high-impact compromise scenario; apply Cisco’s security updates and hardening guidance promptly to reduce the risk of persistent theft of cryptographic keys.
  • Policy research organizations: confirm whether deployed SD‑WAN controllers have been updated since February 2026 and review logs for unusual control-plane activity or communications with external C2 infrastructure, given the framework’s capability to relay commands and files via PolyFlame.

The technical record in this episode is specific and stark: a patched, high‑severity authentication bypass in widely used SD‑WAN controller software was exploited in the wild over multiple years and leveraged to install a framework that targets the cryptographic foundations of network security. Cisco’s updates and hardening guide are the immediate defensive steps the vendor recommends; the facts laid out by Talos and by Lumen’s reporting on the Silent Train framework leave a clear operational task for administrators — apply the patch, look for the artifacts Talos described, and assume that control-plane compromises require a different detection and response posture than conventional perimeter intrusions.

https://www.bleepingcomputer.com/news/security/hackers-exploit-cisco-sd-wan-flaw-to-deploy-custom-keydrift-malware/