Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-76466: Cisco Expressway Cluster Database Root Remote Code Execution

Published Oct 21, 2026 · Updated today
Trending this week#35of 431,986 vulnerabilities
Mention activity · 30 days114 mentions · peak 56 in a dayToday
CVSS9.8Critical · v3.1
EPSS2.2%83rd percentile
CISA KEVYesAdded Nov 20, 2026
In the wildActivePer CISA KEV
Vendor
Cisco Systems
IdentifiersCVE-2026-76466CWE-798 · Use of Hard-coded Credentials

CVE-2026-76466 is a hard-coded credentials vulnerability in the clustering database service of Cisco Expressway Core (Expressway-C) and Expressway Edge (Expressway-E). Persistent Erlang authentication cookies shared across installations of affected releases allow an attacker possessing the relevant cookie to establish a database-service connection and invoke remote procedure calls that execute arbitrary operating system commands as root. Insufficient TLS client-certificate validation leaves the service vulnerable even when clustering TLS Verify Mode is Enabled. The vulnerability affects clustered virtual and hardware deployments; standalone systems are unaffected. Cisco assigns a CVSS v3.1 score of 9.8. Exploitation in the wild has been reported.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can completely compromise the confidentiality, integrity, and availability of an affected appliance through root-level command execution. Attackers can access or modify appliance data and configuration, execute additional tools, and disrupt services. Compromised Expressway nodes can also provide a foothold for internal reconnaissance, attacks against other cluster members, and attempts to obtain credentials or sensitive information from reachable internal services. Reported exploitation compromised four cluster nodes at one organization; successful data exfiltration was not consistently confirmed.

Mitigation

If you can’t patch tonight, do this now.

Cisco states that no workaround addresses the vulnerability. Pending an upgrade, restrict TCP ports 4371 and 4372 to authorized cluster peers, blocking access from the Internet and unauthorized internal networks. These network restrictions reduce exposure but are not an official Cisco workaround. Do not rely on enabling clustering TLS Verify Mode to prevent exploitation. Review cluster-service logs, unexpected peer connections, suspicious scripts, and unusual outbound access to internal services. Isolate systems showing evidence of compromise, preserve evidence, investigate lateral movement, and rotate potentially exposed credentials.

Remediation

Patch, then assume compromise.

Upgrade every affected Expressway cluster node to X15.5.20 or a later Cisco-designated fixed release. Affected X14 and earlier deployments must migrate to a supported fixed release because those branches do not receive a fix. Verify hardware compatibility, available memory, configuration support, and Cisco's upgrade requirements before deployment. Investigate previously exposed systems for compromise: applying the update closes the vulnerability but does not remove access or tooling already established by an attacker.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
cve-2026-76466The repository contains two standalone Python programs and four supporting files: README.md, SECURITY.md, docs/technical-analysis.md, and .gitignore. The main exploit implements Erlang external-term encoding/decoding and describes a TLS distribution client that authenticates with maintenance identity 'wombat@127.0.0.1' and cookie 'wombat'. Its visible CLI supports TLS-only probing, authenticated ping/pong, and a fixed 'id -u' root-execution proof. Node identity and cookie are configurable, but no arbitrary-command option is exposed. This makes it an operational, bounded exploit rather than a framework-integrated or general-purpose command runner. The claimed vulnerability is a hard-coded maintenance credential combined with automatic admission of a 'wombat@'-prefixed node by the Expressway cluster manager. If accepted, the resulting Erlang distribution session allegedly permits operating-system commands in the root-owned VM context. Documentation claims successful testing against Expressway-C X15.3.2 in TLS Permissive mode; Expressway-E, TLS Enforcing mode, older releases, and the claimed fixed release were not tested. The fleet detector accepts individual targets or a line-based fleet file, performs TLS and a simplified authentication exchange, and prints classifications with optional JSON. Its --uid flag only adds instructions for running the main exploit. Its handshake handling is questionable: it treats an initial status message as failure and uses a challenge digest construction inconsistent with standard Erlang distribution authentication. Its classifications should therefore not be treated as reliable vulnerability confirmation without validation. The supplied main exploit is truncated in the middle, preventing full inspection of its handshake and RPC implementation or confirmation of runtime correctness. CVE attribution, advisory details, affected versions, and reported test results are repository assertions, not independently verified findings. No visible malicious local commands, fixed external callback infrastructure, or exfiltration endpoints were identified. Repository URL, git reference, and archive size were not provided; empty metadata and a zero size represent unavailable information.dinosn · Disclosed Nov 5, 2026 · python · networkOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Cisco SystemsExpresswayapplication
FAQ

Frequently asked questions

Is CVE-2026-76466 exploited in the wild?
Yes. As of Nov 22, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 20, 2026.
Is there a public exploit for CVE-2026-76466?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-76466, the earliest disclosed Nov 5, 2026.
Is there a patch for CVE-2026-76466?
Upgrade every affected Expressway cluster node to X15.5.20 or a later Cisco-designated fixed release. Affected X14 and earlier deployments must migrate to a supported fixed release because those branches do not receive a fix.
What products are affected by CVE-2026-76466?
Cisco Systems Expressway.
How severe is CVE-2026-76466?
CVE-2026-76466 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 2.2% (83rd percentile) as of Nov 22, 2026.
Activity feed

Recent activity

135 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
security affairsNews · Nov 21, 2026U.S. CISA adds Cisco Expressway, SAP NetWeaver, Broadcom VMware vCenter, and Apache Roller flaws to its Known Exploited Vulnerabilities catalog - Security AffairsA critical Cisco Expressway Series vulnerability involving hard-coded credentials and insufficient client-certificate validation in clustered deployments. Attackers possessing persistent cookies can access the database service and execute remote procedure calls, potentially running operating system commands as root. Exploitation followed publication of a proof-of-concept and enabled a breach, lateral-movement preparation, and access to sensitive information. The reported CVSS score is 9.8.Read more ↗the hacker newsNews · Nov 21, 2026Hackers Exploit Critical VMware, Cisco, and Apache Flaws as Espionage Attacks EmergeA critical hard-coded credentials vulnerability in Cisco Expressway Series enabling unauthenticated attackers with persistent cookies and network access to execute root commands on a clustered device. Exploited against a Russian organization after a proof-of-concept exploit was released, enabling lateral movement and sensitive-data access. No threat actor attribution was reported. Fixed in October 2026 and added to CISA KEV.Read more ↗cameroon cirtNews · Nov 21, 2026[CRITIQUE] Campagnes actives contre Apache et Cisco - CIRTThe alert describes a hardcoded credentials vulnerability affecting Cisco, reporting active exploitation and CISA KEV inclusion. It recommends applying the Cisco patch and reviewing device configurations. No specific Cisco product or affected version is identified.Read more ↗cysecurity newsNews · Nov 20, 2026Critical Cisco Expressway Vulnerability Exploited By Hackers Shortly After Public PoC Release - CySecurity News - Latest Information Security and Hacking IncidentsA critical vulnerability, rated CVSS 9.8, in the Cisco Expressway database service allows unauthenticated network attackers to execute commands as root on clustered Expressway Core and Edge deployments. The flaw involves persistently stored cookies that can enable database-service access and remote procedure call execution. Attackers compromised a Russian organisation shortly after public exploit code appeared, exploiting two Internet-facing systems running X15.5.3 and moving laterally to two internal cluster nodes. Cisco released patched version X15.5.20. Although Cisco provides no official workaround, F6 recommends restricting TCP ports 4371 and 4372 to trusted cluster-node IP addresses until patching is possible.Read more ↗
+17 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity111Community discussion across Reddit, Mastodon, and other social sources.