CVE-2026-10973
Google Chrome ≤ 149.0.7827.53
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:NSummary
CVE-2026-10973 is a high-severity Use of Uninitialized Variable (CWE-457) vulnerability in Google Chrome. Its CVSS base score is 7.4 (High).
Operationally, ranked in the top 41% of CVEs by exploit likelihood; 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.
The vulnerability is an uninitialized use flaw (CWE-457) in the Dawn component of Google Chrome versions prior to 149.0.7827.53. It carries a CVSS 3.1 score of 7.4 and was rated High severity by the Chromium project, affecting the browser's ability to safely handle certain graphics-related operations before memory initialization occurs.
A remote attacker can exploit the issue by serving a crafted HTML page that triggers the uninitialized memory access. Successful exploitation allows leakage of cross-origin data, with the attack requiring user interaction via the UI but operating over the network with no privileges needed and changed scope in the CVSS model.
The referenced Chrome stable channel update and associated Chromium issue tracker entry indicate that the flaw is resolved by upgrading to version 149.0.7827.53 or later.
The EPSS score has remained flat at 0.0482 with no material rise after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-34422
Vulnerability Data
Uninitialized Use in Dawn in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to leak cross-origin data 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.