Published 21 November 2026 · Rathish Kumar, Invitty
CISA added Cisco Expressway flaw CVE-2026-76466 to its exploited-vulnerabilities list on 20 November 2026. It is a critical flaw (CVSS 9.8) that needs no login and affects Expressway-C and Expressway-E when they run in a cluster. There is no workaround. Upgrade to X15.5.20 or later, and treat any clustered Expressway that stayed unpatched as potentially compromised.
What is CVE-2026-76466 and why does it matter now?
Cisco published the advisory, cisco-sa-vcs-static-cred-hr7EWZ8t, on 21 October 2026 and rated it Critical with a base score of 9.8. The weakness is classed as hard-coded credentials. Cisco describes the cause as persistent cookies combined with weak client certificate checking in the database service that clusters use to talk to each other, when TLS Verify Mode is enabled for clustering. An attacker with network reach to the device and the right cookies needs no account and no user action.
For a month this was a "patch when you can" item. On 20 November CISA put it in the Known Exploited Vulnerabilities catalogue, with a due date of 23 November for US federal agencies and a note that forensic triage is required. When CISA lists a flaw, someone has used it. Cisco's own advisory still says it had no knowledge of malicious use, but that text dates from October and has not been revised.
Which Expressway versions and setups are affected?
Expressway-C and Expressway-E, both virtual and appliance, are affected if they run a vulnerable release and are configured in a cluster. Clusters are common in Indian enterprises that run Expressway for Webex or Cisco Meeting Server mobile and remote access, because two or more nodes give resilience for the edge pair.
| Your release | What Cisco says |
|---|---|
| X15.5.3 and earlier | First fixed release is X15.5.20 |
| X14 and earlier | Migrate to a fixed release; no specific build is named |
| Single node, not clustered | Outside the CVE-2026-76466 condition, still covered by the hardening advisory |
Cisco lists only these two release rows. If you run a newer train, read the live advisory before assuming you are clear.
What should you do first?
Do these in order.
- List every Expressway-C and Expressway-E, and note which are clustered and the version each runs. Check this in the web interface under the system overview, or from your configuration records.
- Restrict access to the cluster and management interfaces to the peer nodes and your admin network while you plan the upgrade. This does not fix the flaw, but it cuts exposure.
- Schedule the upgrade to X15.5.20 or later. Take a configuration backup first, and upgrade nodes in the order Cisco's release notes give for clusters.
- Review logs and admin accounts for anything you cannot explain, especially on Expressway-E, which faces the internet. CISA marks forensic triage as required, so do not stop at patching.
- If you handle regulated data and find signs of compromise, remember CERT-In expects incident reports within 6 hours of noticing them.
What else does X15.5.20 fix?
The same release answers a second advisory, Cisco Expressway Series Security Hardening Release: October 2026. It groups eight CVEs, CVE-2026-76490 to CVE-2026-76497, found in Cisco's internal testing. Scores run up to 8.6 for memory and crash issues, and 7.8 for code injection, permission and temporary file problems. Cisco says these affect every Expressway regardless of configuration, and it is not aware of exploitation. There is no workaround for them either.
That matters for the standalone pair. Even if CVE-2026-76466 does not apply to you, one upgrade closes nine CVEs. We would not defer it.
What it means for budgets and renewals in India
Teams on X14 or older face a migration, not a patch. That usually means a maintenance window, a check that your Cisco support contract is active so you can download the software, and sometimes new virtual machine capacity. If the contract lapsed, fix that first, since downloads of fixed releases depend on entitlement. Ask for support renewals and any new licences on a GST invoice so the cost lands in the right budget line.
My view: if your Expressway pair is older hardware nearing end of life, use this incident to decide between upgrading in place and moving the edge to a supported platform, rather than paying for emergency work twice.
Next step
We supply and support Cisco products and can check your Expressway cluster version, confirm support entitlement through our renewals team, and plan the upgrade window. If you want an outside check for signs of compromise on your internet-facing systems, our VAPT service covers that, and our firewall team can tighten what reaches the edge.
Questions about the Expressway flaw
Is my Cisco Expressway affected if it is not in a cluster?
Is there a workaround for CVE-2026-76466?
Is CVE-2026-76466 being exploited?
Does upgrading to X15.5.20 also fix the other October Expressway flaws?
Not sure if your devices are affected? Send us the model and current firmware or version on WhatsApp, or use the form on this page. We will tell you whether this advisory applies to you and which update to schedule.
Sources
Facts in this post come from these pages, checked on 21 November 2026. Advisories change, so confirm the current text on Cisco's site before you act.