CVE-2026-95376
Google Chrome ≤ 154.0.8037.57
Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-95376 is a high-severity Externally Controlled Reference to a Resource in Another Sphere (CWE-610) vulnerability in Google Chrome. Its CVSS base score is 8.0 (High).
Operationally, ranked at the 9th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-89257
Vulnerability Data
Externally controlled reference in DevTools in Google Chrome prior to 154.0.8037.57 allowed an adjacent attacker leveraging social engineering to bypass system access restrictions via crafted network traffic. (Chromium security severity: Medium)
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Enforces access authorizations so externally supplied references cannot reach resources outside the intended sphere.
Controls information flow between security domains, blocking resolution of external references to unintended spheres.
Monitors and controls boundary communications, limiting the ability of external references to reach protected resources.
Validates information inputs, directly stopping externally controlled names or references from being accepted.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure development lifecycle mandates validation of all external references to prevent uncontrolled resource access.
A.8.26 only requires that security requirements (including those that could address sphere separation) be identified and specified during development or acquisition; it does not itself enforce, implement or mandate any mechanism that stops external references from resolving outside the intended sphere, so the weakness remains exploitable.
A.8.27 mandates security-by-design principles (least privilege, default-deny, distrust-external-input, fail-securely, zero-trust verification) plus design reviews that can catch and stop many externally-controlled cross-sphere references before they reach production, but leaves a bounded remainder (e.g. runtime name resolution, configuration-driven references, or supplier code not covered by the contract) that can still be present and exploitable.
Secure coding standards require input validation and canonicalization to block externally controlled resource references.
Security testing can detect instances of the weakness but does not prevent it at design or coding time.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-610, a class-level weakness, and none of its children carries one either.