Cisco Expressway CVE-2026-76466 in KEV: Patch Clusters
TL;DR · the short version
CISA added CVE-2026-76466, a CVSS 9.8 flaw in Cisco Expressway, to its Known Exploited Vulnerabilities catalog on 20 November 2026, due 23 November with the forensic-triage flag. Cisco's 21 October advisory says an unauthenticated attacker with network access can run commands as root through the database service of clustered Expressway-C and Expressway-E devices; the fix is X15.5.20, X14 and earlier must migrate, and there is no workaround. On 18 November F6 reported the first exploitation case: attackers broke into two internet-facing Expressway X15.5.3 devices at a Russian company soon after a public proof-of-concept appeared, then reached two more cluster nodes on the internal network and ran Python tools to hunt for credentials. Cisco's advisory still said it was unaware of malicious use when we read it on 21 November.
CISA says CVE-2026-76466 in Cisco Expressway is being exploited and gave federal agencies until 23 November 2026 to fix it. CISA added it to the Known Exploited Vulnerabilities catalog on 20 November 2026 with the forensic-triage flag set. Per Cisco's advisory of 21 October, an unauthenticated attacker with network access can run commands as root on clustered Expressway-C and Expressway-E devices (CVSS 9.8); the fix is X15.5.20 and there is no workaround. On 18 November F6 reported attackers breaking into two internet-facing Expressway devices at a Russian company and then reaching two more cluster nodes on the internal network.
Who this is for: CISOs, collaboration and voice teams, and network owners who run Cisco Expressway for remote and mobile access to Unified CM, Webex hybrid services or B2B video. Expressway-E usually sits in the DMZ, so it is often internet-facing by design.
Based on Cisco's advisory, the CVE.org and CISA KEV records, F6's press release and SecurityWeek's report, all read on 21 November 2026. PlayCISO is not affiliated with Cisco or F6. We publish no exploit details.
Confirmed vs not yet known
Cisco confirms (21 Oct): CVE-2026-76466 lets an unauthenticated remote attacker run commands as root through the database service of Expressway devices "configured in a cluster". Fixed in X15.5.20; X14 and earlier must migrate; no workarounds.
CISA confirms exploitation: in KEV since 20 November 2026, due 23 November, forensic triage "Yes", ransomware use "Unknown".
F6 reports (18 Nov): the first exploitation case it investigated, at an unnamed Russian company running X15.5.3, soon after a public proof-of-concept appeared. F6 did not attribute it to a known group, per SecurityWeek.
Not established: who is exploiting it, how many organisations are hit, and who published the proof-of-concept and when. Cisco's advisory had not been revised to mention exploitation when we read it on 21 November.
Affected and fixed versions
| Product | Affected | Fix | Source |
|---|---|---|---|
| Expressway-C and Expressway-E (virtual and appliance), clustered | X15.5.3 and earlier | X15.5.20 | Cisco |
| Expressway, clustered | X14 and earlier | Migrate to a fixed release | Cisco |
| Standalone Expressway | Not affected by this CVE | n/a | Cisco |
Cisco says the flaw comes from "the use of persistent cookies" in the database service, plus client certificates not being validated when TLS Verify Mode is set to Enabled for clustering. The CVE record classes it as CWE-798, use of hard-coded credentials. Cisco credits Stefan Aleksic of Jane Street.
What F6 says the attackers did
- Compromised two internet-facing Expressway X15.5.3 devices, then used one to reach two more cluster nodes on the internal network.
- With root access, prepared Python tools to scan the network, find SMB shares, talk to SQL Server and WinRM, and search GitLab repositories for credentials and sensitive data.
- Edited the scripts during the attack; F6 says comments and fix notes in the code suggest an AI assistant was used.
F6's published indicators: IP addresses 66.179.31[.]32 and 18.130.47[.]116; the line nodeup,'wombat@127.0.0.1' in erlang.log; and Python files at /mnt/harddisk/i{0-9}{4}[a-zA-Z]?/*.py.
Useful next, if this was relevant to you
Timeline
| Date | Event | Source |
|---|---|---|
| 21 Oct 2026 | Cisco publishes advisory cisco-sa-vcs-static-cred-hr7EWZ8t (CVSS 9.8); fix X15.5.20; "not aware of" malicious use | Cisco, CVE.org |
| After 21 Oct | A proof-of-concept exploit is posted on GitHub (author and date not confirmed) | SecurityWeek |
| 18 Nov 2026 | F6 reports the first exploitation case it investigated, with IOCs | F6 |
| 19 Nov 2026 | SecurityWeek reports the exploitation; Cisco's advisory not yet revised | SecurityWeek |
| 20 Nov 2026 | CISA adds CVE-2026-76466 to KEV, due 23 Nov, forensic triage required | CISA KEV |
What security leaders should do this week
- Find every Expressway and check whether it is clustered. Include Expressway-E in the DMZ, Expressway-C inside, lab and disaster-recovery clusters. Standalone devices are not affected by this CVE.
- Upgrade clustered devices to X15.5.20 now. CISA's due date for agencies is 23 November. If you are on X14 or earlier, plan the migration immediately: there is no fix on that line.
- Close the cluster ports until you have patched. F6 advises allowing TCP 4371-4372 only from the IP addresses of the other cluster nodes. Never expose them to the internet.
- Hunt before you declare it clean. CISA set the forensic-triage flag. Check
erlang.logfor the line F6 published, look for the file paths and connections to the two IP addresses, and review what the Expressway accounts and service credentials can reach. Patching does not remove an attacker already on the box. - Assume credentials on or reachable from Expressway are exposed if you find anything. F6 saw attackers hunting for credentials in SMB shares, SQL Server, WinRM and GitLab. Plan rotation with the Key Rotation Planner and run the response in the IR Playbook Lab format.
- Rank and record it. Check it in the KEV checker, set the deadline with the BOD 26-04 calculator, and log any cluster you cannot upgrade this week in your risk register with an owner and a date.
For another recent Cisco flaw, see Cisco ISE CVE-2026-76460; for the vendor view, see Cisco in the Breach Index. CVE-2026-76466 is a vulnerability in Cisco software, not a breach of Cisco.
Frequently asked questions
What is CVE-2026-76466?
CVE-2026-76466 is a critical flaw (CVSS 9.8) in the database service of Cisco Expressway Core and Expressway Edge. Cisco says an unauthenticated remote attacker with network access can run operating system commands as root. It is caused by persistent cookies and by client certificates not being validated when TLS Verify Mode is enabled for clustering. Cisco published it on 21 October 2026.
Is CVE-2026-76466 in the CISA KEV catalog?
Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 20 November 2026 with a due date of 23 November 2026 and the forensic-triage flag set. Known ransomware use is marked "Unknown".
Which Cisco Expressway versions are affected and fixed?
Per Cisco, Expressway-C and Expressway-E (virtual and appliance) running X15.5.3 or earlier are affected only if the devices are configured in a cluster. The fix is X15.5.20. X14 and earlier must migrate to a fixed release. Cisco lists no workarounds.
Is a standalone Expressway affected?
Not by CVE-2026-76466. Cisco's advisory says devices are affected only when configured in a cluster.
Has CVE-2026-76466 been exploited?
Yes, per F6 and CISA. F6 said on 18 November 2026 it investigated the first exploitation case: attackers compromised two internet-facing Expressway X15.5.3 devices at a Russian company soon after a public proof-of-concept appeared, then used one to reach two more cluster nodes on the internal network. CISA added the flaw to KEV on 20 November. Cisco's advisory, as we read it on 21 November, still said Cisco was not aware of malicious use.
What can I do if I cannot upgrade to X15.5.20 today?
Cisco lists no workaround. F6's interim advice is to allow TCP ports 4371-4372 only from the IP addresses of trusted cluster nodes. Treat that as a stopgap: upgrade, and check for compromise because exploitation has been reported.
How do I check whether my Expressway was compromised?
F6 published indicators: the IP addresses 66.179.31[.]32 and 18.130.47[.]116, a log line nodeup,'wombat@127.0.0.1' in erlang.log on Expressway devices, and Python files under /mnt/harddisk/ in directories named i followed by four digits and an optional letter. F6 says the erlang.log line should be confirmed against other logs and artefacts.
Was Cisco hacked?
No. CVE-2026-76466 is a vulnerability in Cisco Expressway software. The exploitation reported is against organisations running unpatched clustered devices, not against Cisco.
Sources
- Cisco: Cisco Expressway Series Remote Code Execution Vulnerability, cisco-sa-vcs-static-cred-hr7EWZ8t (21 October 2026)
- CISA Known Exploited Vulnerabilities catalog: CVE-2026-76466, added 20 November 2026, due 23 November 2026
- CISA BOD 26-04: Prioritizing Security Updates Based on Risk
- CVE.org: CVE-2026-76466 (CNA Cisco; CISA ADP)
- NVD: CVE-2026-76466
- F6: first exploitation of CVE-2026-76466 (18 November 2026, in Russian)
- SecurityWeek: Hackers exploit Cisco Expressway vulnerability soon after PoC release (19 November 2026)