CISA Adds Cisco Expressway Root Command-Execution Flaw to KEV
Quick Answer
Identify affected Expressway clusters and move to X15.5.20 or the supported fixed path. CISA lists November 23 and forensic triage; retain evidence before changing exposed systems.
Confirm Scope And Apply The Supported Remediation
What to do now: Record Expressway-C/E versions, virtual or hardware platform, cluster members, database-service reachability, owners and maintenance paths. Confirm clustering and the exact release. Cisco notes that enabling TLS Verify Mode does not validate client certificates on this vulnerable path. Follow Cisco’s supported upgrade procedure for all affected cluster members. Cisco provides no workaround; plan migration for X14 and older deployments. Confirm each member’s version, cluster health, registrations and representative call flows. Preserve appliance, authentication and network logs for incident triage.
Last verified: 2026-11-21 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Clustered Cisco Expressway-C and Expressway-E |
|---|---|
| Advisory | CISA-KEV-CVE-2026-76466 |
| CVE | CVE-2026-76466 |
| CISA KEV addition date | 2026-11-20 — CISA KEV addition; catalog released 2026-11-20T17:48:39.1516Z. |
| Authority revision date | No separate material revision is stated for this release. |
| Affected versions | Virtual and appliance Expressway-C/E deployments configured in a cluster. Cisco lists X15.5.3 and earlier as affected; X14 and earlier must migrate to a fixed release. |
| Fixed version | Cisco Expressway X15.5.20; X14 and earlier must migrate to an appropriate fixed release. |
| CVSS base score | 9.8 (CVSS v3.1; Cisco PSIRT) |
| CVSS severity | Critical |
| Exploitation status | CISA confirms exploitation in the wild by adding this vulnerability to KEV. Known ransomware campaign use is listed as Unknown.; no exploitation claim is inferred. |
What Changed
CISA added CVE-2026-76466 to KEV and requires forensic triage. The database service can permit root command execution by an attacker with network access and the persistent cookies. The older October 21 Cisco advisory says PSIRT was unaware of malicious use at that time; the newer CISA entry supplies the exploitation evidence.
What To Validate Now
- Inventory. Record Expressway-C/E versions, virtual or hardware platform, cluster members, database-service reachability, owners and maintenance paths.
- Establish applicability. Confirm clustering and the exact release. Cisco notes that enabling TLS Verify Mode does not validate client certificates on this vulnerable path.
- Remediate. Follow Cisco’s supported upgrade procedure for all affected cluster members. Cisco provides no workaround; plan migration for X14 and older deployments.
- Validate. Confirm each member’s version, cluster health, registrations and representative call flows. Preserve appliance, authentication and network logs for incident triage.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Apply the CISA directive and implementation guidance where applicable. Restricting management reachability can reduce exposure but does not replace the fixed software or required forensic review.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
- https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json
- https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-vcs-static-cred-hr7EWZ8t
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.

