TL;DR: Apply Cisco's vendor-issued mitigations for CVE-2026-76466 immediately in line with CISA BOD 26-04 guidance. If patches or mitigations are unavailable, CISA directs agencies to discontinue use of the affected product.
What Is the Vulnerability?
CVE-2026-76466 is a use of hard-coded credentials vulnerability (CWE-798) in the database service feature of Cisco Expressway Series devices. It carries a CVSS 3.1 base score of 9.8 (CRITICAL) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, meaning exploitation requires no privileges, no user interaction, and can be performed remotely over the network with low complexity.
According to the NVD description, two underlying weaknesses combine to create the vulnerability:
- Persistent cookies: The database service uses persistent cookies that do not expire appropriately. An attacker who obtains these cookies can reuse them to authenticate to the database service without valid credentials.
- Insufficient TLS client certificate validation: When TLS Verify Mode is set to Enabled for clustering, client certificates are not actually validated, undermining the intended authentication control.
With a valid set of persistent cookies, an attacker can connect to the database service and invoke specific remote procedure call (RPC) commands, ultimately executing arbitrary commands as root on the underlying operating system of the affected device.
Who and What Is Affected?
The vulnerability affects the Cisco Expressway Series, which Cisco defines as two device families:
- Cisco Expressway Core (Expressway-C) — typically deployed inside the enterprise network to handle internal collaboration traversal.
- Cisco Expressway Edge (Expressway-E) — typically deployed in the DMZ or at the network perimeter to handle external collaboration traffic.
Because Expressway-E devices are frequently internet-facing, they represent a particularly high-risk attack surface. Any Expressway deployment configured for clustering with TLS Verify Mode set to Enabled should be treated as potentially exposed.
Consult the official Cisco Security Advisory and your vendor support portal to confirm which specific software versions are affected and which contain the fix.
What Is the Impact?
A successful exploit of CVE-2026-76466 grants an attacker full root-level control of the underlying operating system on an affected Expressway device. The CVSS score reflects the maximum impact across all three security dimensions:
| Dimension | Rating | Meaning |
|---|---|---|
| Confidentiality | High | All data on the device, including credentials, certificates, and call metadata, can be read. |
| Integrity | High | Configuration, software, and data can be modified or destroyed. |
| Availability | High | The device and any services it provides can be taken offline. |
Beyond the device itself, a compromised Expressway node can serve as a pivot point into internal collaboration infrastructure, potentially exposing calls, meetings, and directory data traversing the system.
This vulnerability was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-11-20, indicating that CISA has determined it meets the criteria for known exploitation. Organizations subject to CISA BOD 26-04 must treat this with the priority that directive specifies.
What Should You Do Right Now?
The required action, as published by CISA in the KEV catalog, is:
- Apply vendor mitigations immediately. Follow Cisco's official advisory instructions. Ensure your remediation approach aligns with CISA BOD 26-04 patching timelines for internet-exposed and internal assets.
- Conduct forensic triage. CISA's KEV entry references "Forensics Triage Requirements." Review those requirements and assess whether affected devices show signs of unauthorized access or anomalous activity in logs related to the database service and RPC invocations.
- Evaluate internet exposure. CISA explicitly notes that stakeholders are responsible for evaluating each asset's internet exposure. Expressway-E devices in DMZs warrant immediate attention. Determine whether the database service port is reachable from untrusted networks and restrict access where possible at the network level while patching proceeds.
- Rotate credentials and certificates. Given the nature of this flaw — persistent cookies and certificate validation bypass — review and rotate any credentials, session tokens, and certificates associated with clustering configurations on affected devices.
- Discontinue use if mitigations are unavailable. Per CISA guidance, if vendor mitigations cannot be applied, the product should be taken out of service rather than left exposed.
Primary sources to consult:
- Cisco Security Advisory (search Cisco's official security advisories portal for CVE-2026-76466)
- CISA KEV Catalog
- CISA BOD 26-04 (referenced in the KEV entry)
How External Security Testing Surfaces This Exposure
Point-in-time external attack surface assessments can help organizations understand their exposure to CVE-2026-76466 before an attacker acts. Specifically, external testing can:
- Identify internet-reachable Expressway devices. Testers can enumerate whether Expressway-C or Expressway-E hosts are discoverable from outside the organization and whether their database service or administrative interfaces are accessible from untrusted networks.
- Detect version and banner information. Passive and active fingerprinting techniques can determine whether discovered Expressway instances are running software versions known to be affected, enabling prioritized remediation decisions.
- Validate network segmentation controls. Testing confirms whether firewall rules, network segmentation, and DMZ policies are actually preventing access to the database service port — a critical compensating control if patching is delayed.
- Assess TLS configuration posture. Reviewers can evaluate the TLS configuration presented by clustering-enabled devices to identify misconfigurations consistent with the certificate validation weakness described in the advisory.
Because this is a point-in-time assessment, any findings reflect the state of the environment at the time of testing. Retesting after applying mitigations confirms that the exposure has been closed.
Sources & further reading: NVD CVE-2026-76466 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: sec.cloudapps.cisco.com, cisa.gov, f6.ru. This advisory contains no exploit code.
Frequently asked questions
Does an attacker need valid login credentials to exploit CVE-2026-76466?
No. The CVSS vector (PR:N, UI:N) and the NVD description both indicate that no prior authentication is required. An attacker who has obtained the persistent cookies used by the database service can connect remotely and issue RPC commands without possessing valid account credentials.
Is this vulnerability being actively exploited?
Yes, based on its inclusion in the CISA Known Exploited Vulnerabilities (KEV) catalog, which was updated with this entry on 2026-11-20. CISA adds vulnerabilities to the KEV catalog when there is credible evidence of active exploitation. No EPSS score data was available at the time this advisory was written.
Are only clustered Expressway deployments at risk?
The NVD description specifically calls out the TLS Verify Mode setting used in clustering as a contributing factor. However, the broader hard-coded credentials and persistent cookie issues affect the database service regardless. All Expressway Series deployments should be evaluated against Cisco's official advisory to determine their risk posture, not just those in clustered configurations.
What is the significance of the CISA BOD 26-04 reference in the required action?
CISA Binding Operational Directive 26-04 establishes mandatory timelines and processes for federal agencies to address vulnerabilities based on their risk level and internet exposure. For KEV-listed vulnerabilities like CVE-2026-76466, the directive assigns aggressive remediation deadlines. While BOD 26-04 is binding only on federal civilian executive branch agencies, CISA recommends all organizations use it as a best-practice framework for prioritizing security updates.