CVE-2026-6311
Google Chrome ≤ 147.0.7727.101
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:HSummary
CVE-2026-6311 is a high-severity Use of Uninitialized Variable (CWE-457) vulnerability in Google Chrome. Its CVSS base score is 8.3 (High).
Operationally, ranked at the 20th 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 SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-6311 is an uninitialized use vulnerability (CWE-457) in the Accessibility component of Google Chrome on Windows versions prior to 147.0.7727.101. The flaw resides in the renderer process and enables a remote attacker who has already compromised that process to potentially escape the Chrome sandbox via a crafted HTML page. Chromium rates it as High severity with a CVSS v3.1 base score of 8.3 (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H).
Exploitation requires a remote attacker to first compromise the renderer process, likely through a separate vulnerability, followed by user interaction such as loading a malicious HTML page over the network. With high attack complexity, no privileges, and changed scope, successful exploitation allows sandbox escape, potentially leading to full system compromise with high impacts on confidentiality, integrity, and availability.
Google addressed the issue in Chrome 147.0.7727.101 via the stable channel update for desktop. Mitigation involves updating to this version or later. Additional details are available in the Chrome Releases announcement at https://chromereleases.googleblog.com/2026/04/stable-channel-update-for-desktop_15.html and the Chromium issue at https://issues.chromium.org/issues/498201025.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-23064
Vulnerability Data
Uninitialized Use in Accessibility in Google Chrome on Windows prior to 147.0.7727.101 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis directly find uses of uninitialized variables before deployment.
Documented development standards and tools can enforce initialization requirements in code.
Engineering principles can mandate explicit variable initialization to avoid uninitialized use.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly catch uninitialized-variable defects via static analysis and code review while the control encompasses many additional development controls.
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.
Security testing can detect uninitialized-variable bugs, but the control is broader.
Secure development life cycle mandates practices that reduce uninitialized-variable defects.
Application security requirements can specify initialization rules, but the control itself does not directly address the weakness.
Secure coding explicitly requires variable initialization and static-analysis checks.
Secure architecture principles encourage defensive coding that can mitigate uninitialized variables.