CriticalVulnerabilityPatch available

Cisco Expressway CVE-2026-76466: root RCE, public PoC, upgrade to X15.5.20

Clustered Cisco Expressway nodes have a critical root RCE flaw, CVE-2026-76466, and a public PoC exists; upgrade to X15.5.20 or a fixed release.

Published
Updated
Fixed in
Cisco Expressway X15.5.20 (for X15.5.3 and earlier); migrate to a fixed release from X14 and earlier
Exploitation
No confirmed exploitation. Cisco PSIRT was not aware of malicious use at publication, and GBHackers reports a public proof-of-concept exploit as of November 12, 2026.

Live scores

CVE-2026-76466
EPSS
0.004
low predicted chance of attack
VEDAS
0.045
little exploit evidence
On CISA KEV
Not listed
Detection rule
No public rule yet
EPSS (chance of attack)
100.1CVE-2026-76466 EPSS over time2026-112026-11-17
VEDAS (exploit evidence)
100.5CVE-2026-76466 VEDAS over time2026-112026-11-17

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.

What happened

On October 21, 2026, Cisco published a Critical advisory for CVE-2026-76466 in Cisco Expressway Series. Cisco rates it CVSS 9.8 and classifies it as CWE-798. According to Cisco PSIRT, an unauthenticated remote attacker with network access to the device could execute arbitrary operating system commands as root through the database service feature. Cisco attributes this to the use of persistent cookies, plus insufficient validation of client certificates when the TLS Verify Mode is set to Enabled for clustering. An attacker who has the cookies could connect to the database service and invoke specific RPC commands. Cisco credits Stefan Aleksic of Jane Street with reporting the issue.

On November 12, 2026, GBHackers reported that a public proof-of-concept exploit and a fleet detector had been posted on GitHub by researcher Nicolas Krassas (dinosn). GBHackers’ technical description, based on the researcher’s analysis and not on Cisco’s advisory, says:

  • The cluster database service uses Erlang/OTP and listens on TCP port 4372 over TLS.
  • Sessions authenticate with a shared cookie, and a hard-coded maintenance identity and matching cookie are compiled into the cm_server module, so they are the same on every installation of the affected release.
  • In TLS Permissive mode, which GBHackers calls the factory default, client certificates are not validated.
  • A client that knows the identity and cookie can complete the handshake and call os:cmd through rpc:call. The researcher’s test command returned 0, which confirms root.

GBHackers also reports the testing was narrow. The researcher validated it only on Expressway-C X15.3.2 in a two-node cluster in TLS Permissive mode. TLS Enforcing mode, Expressway-E, X14 releases and the fixed X15.5.20 build were not tested.

On exploitation, Cisco PSIRT stated it was not aware of public announcements or malicious use at the time of its advisory. GBHackers repeats this and adds that a public PoC could change it. Neither source confirms in-the-wild exploitation.

Am I affected?

Per Cisco PSIRT, you are affected if all of the following apply:

  • You run Cisco Expressway-C or Expressway-E, virtual or appliance.
  • The release is vulnerable: X14 and earlier, or X15.5.3 and earlier.
  • The devices are configured in a cluster.

Cisco lists no other products as affected and does not say whether non-clustered devices are vulnerable beyond the cluster condition above. Whether TLS Enforcing mode prevents exploitation of the public PoC is not confirmed; the researcher did not test it.

What to do now

  1. Inventory your Expressway-C and Expressway-E nodes and identify which are clustered and which release they run.
  2. Upgrade X15.5.3 and earlier to X15.5.20. For X14 and earlier, Cisco says to migrate to a fixed release. Cisco notes the fix is also part of its “Cisco Expressway Series Security Hardening Release: October 2026”.
  3. Do not rely on a workaround: Cisco PSIRT states none exists.
  4. Until patching is done, GBHackers suggests limiting TCP ports 4371 and 4372 to authorized cluster peers and alerting on connections from other addresses. This is GBHackers’ suggestion, not Cisco guidance.
  5. GBHackers also suggests confirming from non-peer networks whether those ports are reachable, and using the researcher’s ping mode, which only authenticates and runs no commands. Review any third-party tool before running it against production systems.

Update, 14 November 2026

  • Cisco tracks the issue under Cisco Bug ID CSCww27732, and the advisory (cisco-sa-vcs-static-cred-hr7EWZ8t) is at Version 1.0 Final, with no revisions since the initial release on 2026-OCT-21. (sec.cloudapps.cisco.com)

Sources