Check these three things.
-
System owner: confirm each Expressway-C and Expressway-E runs X15.5.20 or later.
Affected versions and fixes
- Affected, from Cisco's advisory and the CVE record:
- Expressway X15.5.3 and earlier. First fixed release: X15.5.20.
- Expressway X14 and earlier. Cisco says to migrate to a fixed release.
- Both Expressway-C (Core) and Expressway-E (Edge), virtual and appliance.
- Cisco lists no workaround.
- Record for each Expressway:
- Installed release.
- Source of that record.
- Date checked.
- Affected, from Cisco's advisory and the CVE record:
-
Network owner: confirm whether your Expressways are clustered, and which systems can reach the cluster ports TCP 4371 and 4372.
When the risk applies
- Cisco: only Expressways configured in a cluster are affected. An attacker with network access to the device needs no login.
- Cisco lists vulnerable clustered Expressways as affected and explains the flaw with the database service and the TLS Verify Mode setting for clustering. It does not name ports.
- F6 names TCP 4371 and 4372 and advises allowing them only from trusted cluster nodes.
- In the case F6 investigated, the attackers first broke into two Internet-facing Expressways, then reached two cluster nodes on the internal network.
- Review which systems could reach the cluster ports while a vulnerable release was installed, even if the Expressway is fixed now.
-
Security owner: search Expressway erlang.log for nodeup,'wombat@127.0.0.1' and look for unexpected Python files under /mnt/harddisk.
What the records can show
- Signs F6 reported from the incident it investigated:
- The entry nodeup,'wombat@127.0.0.1' in erlang.log.
- Python scripts under /mnt/harddisk in folders named i followed by four digits, sometimes with a letter.
- IP addresses F6 lists as indicators of compromise: 66.179.31[.]32 and 18.130.47[.]116.
- Records to review:
- Expressway erlang.log and system logs.
- Firewall logs for connections to TCP 4371 and 4372 from outside the cluster.
- Logs of systems Expressway can reach, such as file shares, SQL Server, WinRM and GitLab.
- Limits:
- Clean records do not prove no attack happened.
- Missing records leave the question open.
- Patching does not remove an attacker who is already inside.
- Signs F6 reported from the incident it investigated:
If records show a break-in, start incident response now. Update Expressway whether or not the cluster ports appear restricted.
Do Now
- System owner: update every Expressway-C and Expressway-E to X15.5.20 or later, and migrate any on X14 or earlier.
Proof the update is done
- Completion evidence for each Expressway:
- Release installed after the update.
- Source of that record.
- Date checked.
- Update every node in a cluster, including internal Expressway-C nodes.
- Update Expressways that are not clustered too. Cisco's Expressway Series Security Hardening Release: October 2026 fixes eight more flaw groups, in all Expressway configurations, in the same X15.5.20.
- Completion evidence for each Expressway:
- Network owner: until the update is done, follow F6's advice to allow TCP 4371 and 4372 only from trusted cluster nodes.
What to know
- This step comes from F6. Cisco lists no workaround. Restricting access lowers who can reach the flaw. It is not the fix.
- Apply the restriction on firewalls in front of Expressway-E as well as between network zones.
Do Next
- System owner: review Cisco's October 2026 Expressway hardening release for the other fixes it includes.
What to review
- Cisco says this fix is also part of Cisco Expressway Series Security Hardening Release: October 2026.
- That advisory covers eight more internally found flaw groups, CVE-2026-76490 to CVE-2026-76497, in all Expressway configurations. They are fixed in the same X15.5.20, and Cisco lists no workaround and no known exploitation for them.
- Security owner: recheck Cisco, CISA and CSIRT Italia for changes to the exploitation status.
What to recheck
- Cisco advisory cisco-sa-vcs-static-cred-hr7EWZ8t. Version 1.0 of October 21, 2026 was unchanged when checked on November 20, 2026.
- The CISA Known Exploited Vulnerabilities (KEV) catalog. CISA added CVE-2026-76466 on November 20, 2026 (catalog 2026.11.20), due November 23, 2026.
- CISA's assessment in the CVE record, updated November 20, 2026.
- CSIRT Italia alert AL10/261021/CSIRT-ITA, updated November 20, 2026.
- Date of each recheck.
Check your own records.
- Use your approved AI tool.
- Require evidence. Flag unknowns.
Read the prompt
The reported finding
Expressway database service remote command execution (CVE-2026-76466)
Original advisory →- Required conditions
- Expressway-C or Expressway-E on X15.5.3 or earlier, or X14 or earlier, configured in a cluster, with network access to the device.
- Reported outcome
- Cisco: an unauthenticated remote attacker can run operating system commands as root. Cisco ties the flaw to persistent cookies and to insufficient validation of client certificates when TLS Verify Mode is set to Enabled for clustering, which Cisco says means client certificates are not validated. CVSS 3.1 9.8 Critical; no workaround.
Fix guidance
- Cisco advisory cisco-sa-vcs-static-cred-hr7EWZ8t, version 1.0, October 21, 2026: fixed in X15.5.20; X14 and earlier must migrate to a fixed release. No workaround.
- Exploitation report: F6 (@f6_cybersecurity on Telegram) reported on November 18, 2026 that attackers exploited the flaw at a company in Russia. They broke into two Internet-facing Expressways on X15.5.3, then two internal cluster nodes, and ran custom scripts to look for credentials. F6 names no attacker.
- CSIRT Italia (@csirt_it) alert AL10/261021/CSIRT-ITA, version 1.1 of November 20, 2026, says the flaw is actively exploited.
- Cisco's advisory, unchanged when checked on November 20, 2026, says Cisco is not aware of public announcements or malicious use. Cisco credits Stefan Aleksic of Jane Street with reporting the flaw.
- Exploitation status: CISA (@CISAgov) added CVE-2026-76466 to its KEV catalog on November 20, 2026, with a catalog due date of November 23, 2026. Known ransomware use: Unknown. CISA's entry asks for forensic triage. CISA SSVC in the CVE record, November 20, 2026: Exploitation active, Automatable yes, Technical Impact total. Cisco's advisory does not report exploitation; the sources conflict, and this page does not resolve that.
What IntegrityLab.ai can check
- This advisory does not mean IntegrityLab.ai detects CVE-2026-76466.
- When enabled for an authorized assessment, IntegrityLab.ai's discovery records reachable web services and the server name they return. This gives your administrator a starting point. It does not currently offer a validated check for this CVE, a cluster port test, confirmation of the installed release, or proof of compromise.
- Internal Expressway-C nodes may not be visible to an external assessment. Not seeing them does not show they are unreachable from inside.