The short version
- The flaw. CVE-2026-76466 is rated 9.8 out of 10 and lets an unauthenticated remote attacker with network access run commands as root on clustered Expressway Core and Edge devices. Cisco published fixes in X15.5.20 on 21 October and lists no workarounds.
- The attack. F6 says attackers breached two internet-facing Expressway X15.5.3 devices at a Russian organisation and used one to reach two further cluster nodes on the internal network. They then ran custom Python scripts to scan for systems and credentials.
- The trigger. Proof-of-concept exploit code was published on GitHub, and F6 says the intrusion came shortly afterwards. Cisco's advisory has not been revised and still states that the company is unaware of public announcements or malicious use of the flaw.
- What to do. Patch to a fixed release. Organisations that cannot patch immediately can, on F6's advice, block TCP ports 4371–4372 at the firewall except from trusted cluster nodes, and should check the Erlang system log for signs of exploitation.
Timeline
| Date | Event |
|---|---|
| 21 October | Cisco discloses CVE-2026-76466 and releases fixed Expressway releases, including X15.5.20. |
| 19 November | F6 publishes its report on in-the-wild exploitation of the flaw against a Russian organisation. |
How the attack worked
Cisco disclosed CVE-2026-76466 on 21 October and scored it 9.8 out of 10. The flaw sits in the Expressway database service and involves persistent cookies; Cisco also cites insufficient validation of client certificates when TLS Verify Mode is enabled for clustering. An attacker holding the cookies can reach the database service, issue remote procedure call commands and run code as root. Only clustered deployments of Expressway Core and Edge, virtual or appliance, are affected.
F6, a Russian security firm, says it investigated an attack on a Russian organisation that began with two internet-facing Expressway devices running X15.5.3. From one of them the attackers reached two further cluster nodes on the internal network. With root access they staged custom Python scripts that scanned the network, enumerated SMB resources, queried SQL Server and WinRM, and searched GitLab repositories for credentials and other sensitive data.
F6 says the scripts were modified during the attack, and that their comments and notes about fixes suggest an AI assistant was used to write them. The firm says the intrusion came shortly after proof-of-concept exploit code was posted on GitHub. Cisco's advisory has not been revised and still says the company is unaware of public announcements or malicious use of the flaw.
Who is affected
The victim is described only as a Russian organisation; F6 did not name it. Four Expressway devices were involved: two reachable from the internet and two internal cluster nodes. Any organisation running clustered Expressway Core or Edge on X15.5.3 or earlier, or on X14 and earlier, remains exposed until it moves to a fixed release. Cisco says X15.5.20 resolves the issue.
F6 has not attributed the attack to a known threat actor, and neither source says how much data, if any, left the network. SecurityWeek said it had asked Cisco to comment on F6's findings.
Detection and containment
F6 points to the Erlang system log on Expressway devices as the place to look for exploitation, specifically the string "wombat@127.0.0.1". It also published two IP addresses seen in the attack — 66.179.31[.]32 and 18.130.47[.]116 — and the path pattern /mnt/harddisk/i{0-9}{4}[a-zA-Z]?/*.py where the Python scripts were staged.
Cisco lists no workaround. For organisations that cannot patch immediately, F6 recommends blocking connections to TCP ports 4371–4372 at the firewall, except from the IP addresses of trusted cluster nodes. F6's conclusion is that perimeter devices need both prompt patching and separation from internal systems: "This incident demonstrates that compromise of a perimeter device can open a path for an attacker to an organization's critical systems."
What is not known yet
- Who carried out the attack; F6 did not attribute it to any known threat actor or group.
- How many organisations or devices were affected beyond the single Russian organisation F6 investigated.
- Whether credentials or other sensitive data were actually taken from the internal network.
- When the proof-of-concept exploit was published and how long exploitation had been under way before F6 investigated.
- Whether Cisco has confirmed F6's findings or revised its advisory; SecurityWeek was awaiting comment.
What to do
If you run Cisco Expressway
- Update clustered Expressway Core and Edge deployments to X15.5.20; hosts on X14 or earlier must migrate to a fixed release.
- If you cannot patch immediately, block TCP ports 4371–4372 at the firewall except from the addresses of trusted cluster nodes.
- Search the Erlang system log for "wombat@127.0.0.1" and look for Python files matching /mnt/harddisk/i{0-9}{4}[a-zA-Z]?/*.py.
- Check logs and traffic for 66.179.31[.]32 and 18.130.47[.]116, and isolate any device showing signs of compromise.
If you find signs of compromise
- Determine the scope of the intrusion before returning the devices to normal service.
- Review SMB, SQL Server, WinRM and GitLab access originating from Expressway hosts, which the attackers used to hunt for credentials.
- Change credentials that the compromised devices could reach.
For everyone else
- Segment internet-facing gateways from internal networks and monitor that infrastructure, because the attackers reached internal cluster nodes through an edge device.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.
We email you about this topic only; unsubscribe any time. See our Privacy Policy.