CISA Adds Cisco Expressway Flaw to KEV Catalog: Patch Due Nov 23
CISA added a critical, hard-coded-credential Cisco Expressway flaw to its KEV catalog on Nov 20, 2026, with a federal patch deadline of Nov 23 and no vendor workaround.

CISA added a critical Cisco Expressway Series flaw, CVE-2026-76466, to its Known Exploited Vulnerabilities (KEV) catalog on November 20, 2026, giving federal agencies until November 23, 2026 — just three days — to patch or remove it. The CVSS 9.8 bug, rooted in hard-coded credentials and tracked by Cisco as CSCww27732, lets an unauthenticated remote attacker who has obtained a device's persistent session cookies execute arbitrary commands as root on clustered Expressway-C and Expressway-E systems. Cisco patched it in late October as part of a broader Expressway hardening release; the KEV listing is the federal government's signal that attackers have since put it to use.
Quick facts
- CVE: CVE-2026-76466
- Product: Cisco Expressway Series (Expressway-C and Expressway-E), clustered deployments
- CVSS 3.1: 9.8 (Critical)
- CWE: CWE-798, Use of Hard-coded Credentials
- Added to CISA KEV: November 20, 2026
- Federal patch-by date: November 23, 2026
- Fix: Upgrade to Expressway X15.5.20 (or a later fixed release); no workarounds exist
What CISA Added to the KEV Catalog
On November 20, 2026, CISA listed CVE-2026-76466 — which it titles the "Cisco Expressway Series Use of Hard-coded Credentials Vulnerability" — in its Known Exploited Vulnerabilities catalog. Per the catalog's own entry, the flaw lets an unauthenticated remote attacker who holds a device's persistent cookies and has network access reach a clustered Expressway's database service and run commands as root. CISA's required action is direct: apply Cisco's fix, follow the BOD 26-04 directive and its forensic triage requirements, confirm whether any affected asset is internet-exposed, and discontinue use of the product if no mitigation can be applied. The due date is November 23, 2026 — two days out from CISA's catalog addition and arriving fast even by KEV standards.
Inclusion in the KEV catalog is not a theoretical designation. CISA's own standard for the list is that it covers vulnerabilities "that have been exploited in the wild," so the November 20 addition is itself federal confirmation that CVE-2026-76466 has moved from patched-but-quiet to actively abused, roughly a month after Cisco first shipped a fix. The catalog entry does not classify the bug as tied to ransomware activity; that field is marked "Unknown."
The Vulnerability: CVE-2026-76466 Explained
Cisco's own advisory, published October 21, 2026 under the ID cisco-sa-vcs-static-cred-hr7EWZ8t, titles this the "Cisco Expressway Series Remote Code Execution Vulnerability" and scores it 9.8 out of 10 on CVSS 3.1 (vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) — network-reachable, low attack complexity, no privileges or user interaction required, and full loss of confidentiality, integrity and availability if exploited. Cisco classifies the root cause as CWE-798, use of hard-coded credentials.
The bug sits in the database service feature of Expressway Series software. According to Cisco, it stems from the product's use of persistent cookies combined with insufficient validation of client certificates when a cluster's TLS Verify Mode setting is left at its "Enabled" value — meaning client certificates presented to the database service are not actually checked. An attacker who has somehow obtained a valid device's persistent cookies can connect directly to the database service and invoke specific remote procedure call (RPC) commands, which Cisco says is enough to execute arbitrary operating system commands with root privileges on the underlying appliance or virtual machine.
The CVE.org record for CVE-2026-76466 tracks the same identifier under Cisco as the assigning authority.
Cisco credits Stefan Aleksic of Jane Street with reporting the issue, and as of the advisory's last published revision, Cisco PSIRT states it is "not aware of any public announcements or malicious use" of the flaw. That line has not changed in the version history shown on Cisco's page, which still reads "Version 1.0: Final" with no later revision. CISA's KEV addition a month later is the clearest public signal yet that the calculus has changed in practice, even though Cisco's own advisory text has not been updated to say so.
Who Is Affected
Cisco's advisory limits the vulnerable scope narrowly: Expressway-C and Expressway-E, in both virtual and physical appliance form, are affected only when they are running a vulnerable software release and are configured in a cluster. Standalone Expressway deployments are not listed as vulnerable in the advisory. That distinction matters for triage — a lone Expressway-E sitting at the network edge without a cluster partner falls outside the advisory's stated scope, while any clustered pair or group is squarely in it.
| Cisco Expressway Series release | Affected? | First fixed release |
|---|---|---|
| X14 and earlier | Yes (in cluster configurations) | No specific fix listed — migrate to a supported, fixed release |
| X15.5.3 and earlier | Yes (in cluster configurations) | X15.5.20 |
| X15.5.20 and later | No | — (already fixed) |
Cisco states there are no workarounds for this vulnerability — disabling clustering or changing the TLS Verify Mode setting is not offered as a mitigation in the advisory. The only remediation path Cisco lists is upgrading to a fixed release.
How This Compares to Other Recent Expressway Advisories
CVE-2026-76466 did not arrive alone. Cisco published it alongside a separate bulletin, "Cisco Expressway Series Security Hardening Release: October 2026," which documents a set of additional, internally discovered hardening improvements across the product line. The X15.5.20 release that fixes CVE-2026-76466 also carries those hardening changes, so administrators upgrading for this KEV entry are picking up the broader round of fixes in the same release. Cisco groups security advisories like these under regular bundled-disclosure dates, visible on its own Security Advisories listing page, which is also the pattern behind other entries this desk has covered recently, including a Cisco BroadWorks XXE flaw CISA added to the KEV catalog and a critical Cisco ASA and FTD VPN vulnerability that drew a similarly compressed federal deadline.
What Cisco Says vs. Unverified Reports of Exploitation
There is a real gap between Cisco's published position and what has circulated since. Cisco's advisory, unchanged since its October 21 "Final" release, says PSIRT has no awareness of public exploitation. But CISA's KEV criteria require evidence of active exploitation before a CVE is added, and that addition landed on November 20 — a month after the patch shipped.
Separately, and importantly unconfirmed by either Cisco or CISA, secondary security-industry reporting has described a specific incident. A cybersecurity research firm has claimed to have identified what it calls the first known real-world exploitation of this flaw, saying attackers compromised a small number of internet-facing, clustered Expressway devices running X15.5.3 belonging to an unnamed organization, used that foothold to reach other nodes in the same cluster, and then used root access to stage reconnaissance tooling aimed at internal file shares, database servers, and credential-bearing code repositories. That reporting also describes public proof-of-concept exploit code as having circulated before mid-November 2026. None of these specifics — the scope of the intrusion, the tooling details, or the proof-of-concept timeline — appear in Cisco's own advisory, and Pandromeda has not independently verified them. Readers and defenders should treat them as reported, not established, and should rely on Cisco's and CISA's own published material for anything that drives a compliance or disclosure decision.
The KEV Catalog and the Federal Deadline
For civilian federal agencies, a KEV catalog listing is not advisory — Binding Operational Directive requirements compel action by the stated due date. CISA's entry for CVE-2026-76466 points agencies to apply Cisco's mitigation, carry out the forensic triage steps required under BOD 26-04, and determine whether any affected device is reachable from the internet; if no mitigation can be applied, CISA's required action is to take the product out of service entirely. The KEV catalog's underlying data feed lists the add date as 2026-11-20 and the due date as 2026-11-23, a three-day window that is on the short end even for Critical-severity KEV entries.
Private-sector organizations are not bound by the directive, but security teams generally treat a KEV listing as a strong signal to prioritize the same way federal agencies are required to. With a 9.8 CVSS score, no workaround, and root-level impact on any exposed cluster node, this is a reasonable one to move to the front of the patch queue regardless of sector.
How to Patch Cisco Expressway
Remediation here is simple to state and should be treated as urgent to execute:
- Identify every Expressway-C and Expressway-E instance in your environment, and note which ones are configured in a cluster (standalone instances are outside the advisory's stated scope).
- Check the running software release against Cisco's fixed-release table above.
- If you are on X15.5.3 or earlier, upgrade to X15.5.20 or a later fixed release.
- If you are on X14 or earlier, migrate to a currently supported, fixed release rather than attempting an in-place patch — Cisco does not list a direct fixed build for the X14 branch.
- Because there is no workaround, do not treat changes to TLS Verify Mode, firewalling, or cluster topology as a substitute for the upgrade; they are not offered as mitigations in Cisco's advisory.
- Confirm entitlement and pull the fixed image through Cisco's standard download and TAC channels if you do not already have access.
Checking for Signs of Compromise
Given that this CVE is now in the KEV catalog, administrators of clustered Expressway deployments — especially any node reachable from the public internet — should treat patching as the first step, not the last. Useful checks include reviewing database-service and cluster-replication logs for unexpected or malformed RPC calls, auditing for new or unfamiliar local accounts and cron jobs created after the device's last known-good patch date, checking outbound connections from Expressway nodes for traffic to unfamiliar destinations (particularly anything resembling internal network scanning or SMB, database, or remote-management protocol probing), and rotating any credentials or cluster keys that could plausibly have been exposed if a node was compromised. CISA's BOD 26-04 forensic triage requirements, referenced directly in the KEV entry, give federal agencies a specific checklist to follow; private organizations can use the same categories as a starting point even without the compliance obligation.
Why This Matters Beyond One Advisory
Expressway sits at the edge of an organization's unified-communications stack by design — it is the component built to broker voice and video sessions between internal systems and the outside world, which means a clustered, internet-facing Expressway-E is exactly the kind of asset attackers look for: reachable, trusted by the rest of the cluster, and capable of root-level compromise through a single credential-handling flaw. That combination — edge-facing collaboration infrastructure, a hard-coded-credential root cause, and a fast-moving federal deadline — has now shown up repeatedly across Cisco's security advisories this year, including in a Cisco Secure Email Gateway flaw CISA added to KEV weeks earlier. Whether or not the specific intrusion details now circulating in industry reporting hold up, the pattern of "patch ships quietly, exploitation surfaces within weeks, KEV listing follows" is one defenders of Cisco collaboration and security infrastructure should plan around rather than treat as a one-off.
What to Do Now
- Inventory first. Identify every clustered Expressway-C and Expressway-E node in your environment and flag any that are internet-reachable.
- Patch to X15.5.20 or later on any node running X15.5.3 or earlier; migrate off X14 and earlier entirely.
- Do not wait on a workaround. Cisco has not published one, so upgrading is the only remediation path.
- Follow BOD 26-04 forensic triage steps if your organization is a federal civilian agency bound by the directive, and consider the same checks voluntarily if you are not.
- Review logs and rotate credentials on any node that was internet-exposed and unpatched during the window between Cisco's October 21 fix and today, given unconfirmed reports of exploitation activity in that period.
- Track Cisco's advisory for updates. If Cisco revises cisco-sa-vcs-static-cred-hr7EWZ8t to acknowledge exploitation, that revision will carry more authoritative detail than any secondary report circulating now.
Frequently asked questions
What is CVE-2026-76466?
It is a critical vulnerability in Cisco Expressway Series (Expressway-C and Expressway-E) caused by use of hard-coded credentials (CWE-798). It lets an unauthenticated remote attacker who holds a device's persistent cookies reach the database service on a clustered Expressway and run commands as root. Cisco scores it CVSS 3.1 9.8.
Why did CISA add it to the KEV catalog, and what is the deadline?
CISA added CVE-2026-76466 to its Known Exploited Vulnerabilities catalog on November 20, 2026, which under CISA's own criteria means it has evidence the flaw is being exploited in the wild. Federal civilian agencies have until November 23, 2026 to patch, mitigate, or remove the affected product.
Which Cisco Expressway versions are affected?
Cisco's advisory lists Expressway-C and Expressway-E, both virtual and appliance versions, as affected only when running a vulnerable release and configured in a cluster. Releases X15.5.3 and earlier are fixed in X15.5.20; X14 and earlier have no listed fix and must be migrated to a currently supported release.
Is there a workaround if I cannot patch immediately?
No. Cisco's advisory states there are no workarounds for this vulnerability. The only remediation path Cisco provides is upgrading to a fixed software release.
Has this vulnerability actually been exploited?
Cisco's advisory, last revised October 21, 2026, says Cisco PSIRT is not aware of public announcements or malicious use. However, CISA's KEV catalog only lists vulnerabilities with evidence of real-world exploitation, and some security researchers and outlets have separately reported an intrusion tied to this CVE. Those reports have not been confirmed by Cisco and should be treated as unverified pending an update to Cisco's own advisory.
Are standalone (non-clustered) Expressway deployments affected?
Cisco's advisory describes the vulnerability as affecting Expressway-C and Expressway-E only when they are configured in a cluster. Standalone deployments are not listed as vulnerable, though Cisco still recommends upgrading to the fixed release, which also includes unrelated hardening improvements.
Sources
- CISA: Known Exploited Vulnerabilities Catalogcisa.gov
- CISA KEV Catalog data feed (JSON)cisa.gov
- Cisco Security Advisory: cisco-sa-vcs-static-cred-hr7EWZ8tsec.cloudapps.cisco.com
- Cisco Expressway Series Security Hardening Release: October 2026sec.cloudapps.cisco.com
- Cisco Security Advisories listingsec.cloudapps.cisco.com
- CVE.org record: CVE-2026-76466cve.org
Sana Qureshi runs the security and privacy desk. She reports on actively exploited vulnerabilities, vendor patches and data breaches, and covers the password managers, VPNs and authentication tools readers use to protect themselves. Her alerts cite vendor advisories, CISA and the CVE record directly.

