CISA added CVE-2026-76466 on November 20, 2026 for Cisco Expressway Series—use of hard-coded credentials (CWE-798) on the database service in clustered deployments. Cisco advisory cisco-sa-vcs-static-cred-hr7EWZ8t rates Critical CVSS 9.8 and documents root-level RPC command execution for an unauthenticated remote attacker with network access and persistent cookies.
Expressway sits on the collaboration perimeter—often maintained by a different team than the laptops where coding agents run. KEV makes it patch-now infrastructure anyway.
Facilities tickets labeled "video glitch" should not defer this patch: the vulnerability is root on the appliance, not jitter on RTP. Teach helpdesk staff the difference so social pressure does not push Expressway upgrades into January. Add Expressway version to the same quarterly asset survey agents already generate for laptops so collaboration gear never disappears from inventory spreadsheets again.
TL;DR
| Question | Answer |
|---|---|
| Products | Expressway-C / Expressway-E (virtual or appliance) clustered |
| Fix | X15.5.20+ (migrate off X14 and earlier) |
| Workaround? | None |
| KEV due | 2026-11-23 |
| BOD forensics? | Yes |
| Cisco Oct. statement | No public malicious use at advisory v1.0 — CISA KEV overrides priority |
Mechanism step by step
From Cisco's advisory:
- Clustered Expressway nodes run a database service for configuration replication.
- Persistent cookies (hard-coded credential pattern) and insufficient client certificate validation when TLS Verify Mode is Enabled for clustering weaken mutual authentication.
- Attacker connects to the database service and calls RPC interfaces.
- Successful exploitation runs arbitrary OS commands as root on the appliance.
Scope note: Cisco says only clustered vulnerable releases are affected; standalone posture still merits version audit because clustering is common on production interop edges.
Fixed software
| Release line | Action |
|---|---|
| X14 and earlier | Migrate to fixed release |
| X15.5.3 and earlier | Upgrade to X15.5.20 |
| Hardening bundle | See Expressway Series Security Hardening Release: October 2026 linked from the advisory |
Cisco credits Stefan Aleksic (Jane Street) for reporting. Bug id CSCww27732.
CISA vs Cisco exploitation messaging
Cisco's October 21, 2026 advisory Exploitation and Public Announcements section states PSIRT was not aware of malicious use at that time. CISA's November 20 KEV entry classifies the flaw as known exploited. For incident response, assume active interest and complete BOD 26-04 forensics where applicable while reviewing Expressway and Cisco Unified Communications Manager adjacent logs.
What this means if you run AI coding agents
Coding agents rarely own Expressway, but they increasingly generate infrastructure-as-code for hybrid work (firewall rules, API credentials, automation playbooks):
- Do not let an agent mark Expressway "defer" because traffic is UDP/SIP—this bug is management/database plane.
- After upgrade, re-run
show versionequivalents or REST inventory scripts agents maintain. - If agents store Expressway admin cookies in
.envfor "quick tests," rotate them post-patch—persistent cookie theft is in the attack chain Cisco describes.
Pair with Cisco ASA KEV history for perimeter context; Expressway is another Cisco edge node in the same November KEV batch as vCenter.
Beam monitors agent actions on developer workstations only. It does not terminate Expressway RPC. Use local policy to stop agents from checking admin passwords into git alongside UC diagrams.
Clustering prerequisites (why "we only use Expressway-E" may still fail)
Cisco's vulnerable-products section targets clustered Expressway-C and Expressway-E on vulnerable releases. Many enterprises cluster two nodes for UCM traversal high availability even when operators think of them as "just video relays." Inventory questions agents should script:
- Is neighbor zone clustering enabled?
- Is database replication status healthy in the admin UI?
- Are nodes on X15.5.3 or earlier?
Standalone nodes still deserve patching—future clustering or restored backups may reintroduce vulnerable pairs.
TLS Verify Mode and certificate validation
Cisco's summary links two weaknesses:
- Hard-coded / persistent cookies on the database service path
- Client certificates not validated when TLS Verify Mode is Enabled for clustering
That combination is worse than either alone: an attacker who obtains cookie material (leak, backup, or MITM on mis-segmented mgmt net) can speak RPC as if clustered. After upgrade to X15.5.20, revalidate:
- Certificate rotation schedule—agents should not disable verification "temporarily"
- Cluster join procedures in docs agents rewrite—compare to Cisco hardening guide
Upgrade planning for collaboration edges
Expressway outages break B2B SIP, Teams CIV, and Jabber MRA paths. Planning steps:
- Read October 2026 Expressway hardening release notes linked from the advisory.
- Schedule active/standby upgrades with Cisco's clustered upgrade order.
- Notify video bridge owners—CI agents may fail if ICE paths change during reboot.
- Capture pre-upgrade config export; verify backup not stored in git with secrets an agent indexed.
Threat modeling for coding-agent estates
Attackers gaining root on Expressway can:
- Pivot toward UCM, CUCM, or Webex integrations documented in the same admin space
- Capture signaling metadata even if media stays encrypted elsewhere
- Plant persistence in trusted TLS material agents might later copy into templates
Coding agents are unlikely to exploit CVE-2026-76466 directly, but they amplify post-compromise harm when they sync Expressway configs to shared drives without review.
Comparison with Cisco ASA KEV (same vendor month)
| Item | ASA FTD CVE-2026-76418 | Expressway CVE-2026-76466 |
|---|---|---|
| Surface | SSL VPN / firewall | Collaboration edge |
| Auth model | Session reload bugs | Cluster DB RPC |
| Workaround | Vendor mitigations existed | None |
| Agent ownership | Often network team | Often collab team |
Run one coordinated change window if the same agent maintains Ansible for both—avoid half-patched Cisco perimeters.
Root cause in plain language (CWE-798)
CWE-798 Use of Hard-coded Credentials does not always mean a password printed in source for humans to read. Cisco ties the issue to persistent cookies on the database replication service plus broken certificate validation when clustering TLS is supposedly strict. Attackers combine something you know/hold (cookie material) with RPC interfaces intended only for cluster peers. After patch, rotate clustering credentials and reissue certs if your runbook predates X15.5.20.
Expressway in hybrid work architecture
Expressway-C typically sits inside; Expressway-E DMZ-facing. Video traffic may be UDP-heavy, but this vulnerability is TCP management plane on the database service. Firewall rules that only audit SIP/RTP miss the risk. Ask agents updating Visio/Lucid diagrams to label management interfaces separately from media paths.
Post-patch validation script ideas
Human operators (not blind agent runs) can:
- Confirm software version displays X15.5.20 or later on both cluster members
- Review recent config backups for unexpected admin additions
- Check database service logs around patch window for RPC errors from foreign IPs
- Ensure no Terraform state still references pre-patch API tokens checked into git by agents
Reader checklist for collaboration engineers
- Export show status / version from both cluster members before maintenance.
- Validate maintenance window with video bridge owners and MRA users.
- Apply X15.5.20 (or migrate off X14) per Cisco table—do not stop at interim X15.5.4 if below .20.
- Re-enable clustering only after certificates match Cisco hardening guidance.
- Rotate admin passwords and API credentials stored in password vaults agents sync.
- Review database service bind addresses—should not face untrusted networks.
- File forensic triage evidence if BOD scope includes your org.
Closing operational note
Video collaboration infrastructure carries psychological "availability first" bias—teams fear patch-induced MRA outages more than latent database RPC bugs. CVE-2026-76466 flips that calculus: root on Expressway can persist quietly while calls still connect. CISA's KEV flag should move Expressway upgrades into the same emergency queue as firewall patches, even when no executive is complaining about dropped meetings.
Cisco's October advisory language (no known malicious use) versus CISA's November listing is a teaching moment for agentic risk scoring. Automated triage must ingest KEV feeds as first-class inputs, not optional metadata. Otherwise an agent might downgrade a 9.8 finding because a vendor paragraph sounded calm in Q3.
Operationally, treat cookie theft and cluster TLS mis-validation as combined prerequisites: hardening only cookies without fixing cert validation—or vice versa—leaves assumptions attackers already chain in the wild. After upgrading, run an internal pen test focused on database replication ports from a non-cluster VLAN; if RPC responds, segmentation failed.
Coding agents maintaining Terraform Cisco providers should pin to documented fixed versions and add post-apply hooks that assert version strings, not merely apply succeeded. Success without version proof is how half-patched clusters survive overnight automation.
Document who owns Expressway in your service catalog—when ownership is split between network and collaboration, agents get contradictory patch instructions. A single named team should sign X15.5.20 completion and attach CLI version output to the change record.
If your organization records security awareness metrics, use this KEV as a case study: CVSS 9.8 collaboration gear can be more urgent than a medium desktop app bug, even when users see no outage. That prioritization lesson keeps agent triage honest.
Reserve war-room bridge numbers that do not depend on Expressway MRA paths—if you must patch during business hours, executives need alternate mobiles when split-brain risk is elevated. Communicate that short call blips beat silent root compromise lingering on the edge pair. Store offline runbooks (PDF on file share) listing TAC case templates in case agents cannot reach Cisco portals during the maintenance window. Include serial numbers and smart licensing status so overnight operators are not blocked waiting for a web UI an agent cannot scrape reliably under heavy load.
Frequently asked questions
What is Cisco Expressway?
Expressway-C (core) and Expressway-E (edge) provide firewall traversal and B2B video/voice interop—common in Webex/Teams deployments.
Is CVE-2026-76466 authentication bypass?
CISA categorizes hard-coded credentials; Cisco describes unauthenticated RPC as root with cookies and network access.
How to update Cisco Expressway?
Download X15.5.20 from Cisco Software Center per your support contract; follow Cisco upgrade guide for clustered pairs (maintenance window, backup).
Related reading
- Cisco ASA FTD exploited SSL VPN bug
- VMware vCenter KEV auth bypass
- SAP NetWeaver JNDI KEV
- CrowdStrike Falcon Guardian and agent kill switches
Primary sources: Cisco advisory cisco-sa-vcs-static-cred-hr7EWZ8t, CISA KEV, CVE-2026-76466 at NVD
Advisory versions reflect Cisco and CISA as of November 20, 2026.

