Cisco Expressway CVE-2026-76466: Critical Flaw Now Exploited
CISA confirms attackers are exploiting CVE-2026-76466 in clustered Cisco Expressway, a 9.8-rated flaw that allows root command execution. A fix is available; there is no workaround.
On 20 November 2026, CISA added CVE-2026-76466, a critical flaw in Cisco Expressway, to its Known Exploited Vulnerabilities catalog, with a due date of 23 November [1][2]. Cisco rates it 9.8 (Critical) and says it can let an unauthenticated, remote attacker run commands as root on Expressway-C and Expressway-E devices configured in a cluster [3]. Cisco has a fixed release and lists no workaround [3]. If you run clustered Expressway for remote calling and video, update it now and then check it for signs of earlier access.
What has been confirmed
- CISA: CVE-2026-76466 is in the KEV catalog, added 20 November 2026 with a due date of 23 November [1][2]. CISA describes it as a use of hard-coded credentials that "allows an unauthenticated, remote attacker with persistent cookies and network access to execute commands as root on a clustered device via the database service", and marks it for forensic triage [2].
- Cisco: Advisory cisco-sa-vcs-static-cred-hr7EWZ8t, first published 21 October 2026, rates the flaw 9.8 [3]. Cisco says it affects Expressway-C and Expressway-E, virtual and appliance versions, "if they are running a vulnerable release and have the devices configured in a cluster" [3]. It traces the cause to persistent cookies and insufficient validation of client certificates when TLS Verify Mode is enabled for clustering [3].
- Fixed releases [3]:
- Release X15.5.3 and earlier: update to X15.5.20.
- Release X14 and earlier: migrate to a fixed release.
- The fix is also part of Cisco's Expressway Series Security Hardening Release of October 2026.
- Cisco's table does not map every release. If you run a release it does not list, confirm with Cisco.
- Workarounds: "There are no workarounds that address this vulnerability," Cisco says [3].
- Exploitation: Cisco's advisory, unchanged since 21 October, still says its PSIRT "is not aware of any public announcements or malicious use" [3]. CISA's catalog listing on 20 November is the confirmation of exploitation [2]. No threat actor has been named.
Why this matters
Expressway sits at the edge of the network so that remote staff, partners and video endpoints can reach an organization's Cisco calling and meeting systems. That position makes it reachable from the internet by design, and root access to it gives an attacker a foothold inside. The flaw has had a fix since October, so any device still exposed has missed a month of patching. CISA's three-day deadline means it should move to the top of the list.
What to do now
- Find every Expressway you run, including Expressway-E at the network edge and Expressway-C inside, and check whether they are configured in a cluster [3].
- Update to a fixed release. Move release X15.5.3 and earlier to X15.5.20, or apply the October 2026 security hardening release; migrate X14 and earlier [3]. There is no workaround [3].
- Confirm your release with Cisco if it is not in Cisco's table [3].
- Check for signs of earlier access. CISA flags this flaw for forensic triage [2]. Review Expressway logs going back to October, when the flaw was disclosed, for unexpected administrative sessions, configuration or account changes, and outbound connections you cannot explain, and compare cluster peers for differences.
- Rotate credentials held on or passing through the device if you find anything suspicious.
If you are an MSP or MSSP
Check whether any client runs clustered Expressway, often as part of a Cisco calling or video deployment, and confirm their release. Patch the internet-facing Expressway-E devices first.
Frequently asked questions
Is CVE-2026-76466 being exploited?
Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 20 November 2026 [1][2]. Cisco's advisory has not been updated since 21 October and still says Cisco is not aware of malicious use [3].
Is there a fix?
Yes. Cisco lists X15.5.20 for release X15.5.3 and earlier, and the fix is in its October 2026 Expressway security hardening release [3].
Is there a workaround?
No. Cisco says there are no workarounds [3].
Am I affected if my Expressway is not clustered?
Cisco says Expressway-C and Expressway-E are affected when they run a vulnerable release and are configured in a cluster [3]. If you are unsure, check your configuration and update anyway.
What should an organization without a dedicated security team do first?
Ask whoever manages your Cisco calling or video system whether you run Expressway and which release it is on, and get it updated before 23 November [2][3].
Who is behind the attacks?
No one has been named [2][3].
How Vijilan helps
Vijilan's SOC watches the internet-facing systems attackers reach first, including remote-access and collaboration gateways, around the clock, with machine speed where speed wins and a human approving the actions that carry real risk. ThreatRespond™ runs that on the security tools you already have, for organizations directly and for the MSPs that serve them. Talk to us.
Sources
Threat notes, once a week
What our SOC actually saw this week: new attack patterns, the detections we shipped against them, and what it means if you run an MSP. Written by the analysts, not by marketing.
ThreatDefend™
Our stack. Our SOC.
Managed XDR on CrowdStrike Falcon, deployed and run 24/7 by the Vijilan SOC.