CVE-2026-11668
Google Chrome ≤ 149.0.7827.102
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:NSummary
CVE-2026-11668 is a medium-severity Use of Uninitialized Variable (CWE-457) vulnerability in Google Chrome. Its CVSS base score is 4.3 (Medium).
Operationally, ranked at the 9th 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.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-35268
Vulnerability Data
Uninitialized Use in Codecs in Google Chrome on Linux, ChromeOS prior to 149.0.7827.103 allowed a remote attacker to leak cross-origin data via a crafted video file. (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.