Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-76466 is a critical-severity Use of Hard-coded Credentials (CWE-798) vulnerability in Cisco Expressway Series (inferred from references). Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique SSH (T1021.004); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-5 (Authenticator Management) and SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
Advisories
- Advisory: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks (Nov 19)
- Press: Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release (Nov 19)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-107382
Vulnerability Data
A vulnerability in the database service feature of Cisco Expressway Series could allow an unauthenticated, remote attacker with network access to a Cisco Expressway device to execute arbitrary operating system commands as root. This vulnerability is due to the use of…
more
persistent cookies. Additionally, there is insufficient validation of client certificates when the TLS Verify Mode is set to Enabled for clustering, which means that client certificates are not validated. An attacker with possession of the cookies could exploit this vulnerability by connecting to the database service and invoking specific remote procedure call (RPC) commands. A successful exploit could allow the attacker to execute arbitrary commands as root on the underlying operating system of an affected device. Note: Cisco Expressway Series refers to Cisco Expressway Core (Expressway-C) devices and Cisco Expressway Edge (Expressway-E) devices.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Authenticator management requires secure distribution and handling of credentials, structurally discouraging hard-coded values.
Cryptographic key management mandates proper establishment and handling instead of embedding keys in code.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
PR.AA-01's credential/key-management processes can reduce the incentive to embed secrets but do not address or detect hard-coded values in source code, so the weakness remains fully possible.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
created from the owner's anchor; an owner grade is a row and does not wait for an instrument (Mythos 2026-09-29T15:58Z).
Education on secure configuration practices discourages technical staff from embedding or relying on hard-coded credentials in systems and applications.
A.8.24's key management guidance (generation, storage, distribution through proper processes) prevents hard-coded cryptographic keys in first-party code, but the clause addresses cryptography, not authentication credentials, so the password variant of CWE-798 is untouched; third-party and COTS components with embedded credentials are also outside its reach.
Explicit prohibition of hard-coded passwords and unauthenticated external services stops credentials from being embedded directly in source code.
A.8.30 carries its effect through the secure-coding practices (A.8.28) its contract requires of the supplier, which reduces hard-coded credentials in delivered code the way those practices do; the clause depends on the supplier actually implementing secure coding, and secure coding is a fallible practice, so a minority of instances are prevented.
A.8.8's reach is DISCLOSURE — vulnerability scanning, component inventory, and published advisories — which surfaces hard-coded credentials only where they appear as disclosed flaws in third-party components; most CWE-798 instances live in first-party code or are never published, which A.8.8 does not reach.