Contact us
← Article questionsDoes this affect us?

CVEHit Business Advisory by IntegrityLab.ai

Does this affect us?

Clustered Cisco Expressway flaw lets attackers run commands as root without signing in — CVE-2026-76466: Business Triage

Check these three things.

  1. 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.
  2. 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.
  3. 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.

If records show a break-in, start incident response now. Update Expressway whether or not the cluster ports appear restricted.

← Back to article questions

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…