CVE-2026-5277
Google Chrome ≤ 146.0.7680.177
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2026-5277 is a high-severity External Control of Assumed-Immutable Web Parameter (CWE-472) vulnerability in Google Chrome. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 17th 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 SI-10 (Information Input Validation) — 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-5277 is an integer overflow vulnerability (CWE-472) in the ANGLE graphics component within Google Chrome on Windows versions prior to 146.0.7680.178. The flaw enables an out-of-bounds memory write when processing a crafted HTML page. Chromium security severity is rated as High, with a CVSS v3.1 base score of 7.5 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H), reflecting network accessibility, high attack complexity, no privileges required, user interaction needed, unchanged scope, and high impacts on confidentiality, integrity, and availability.
The vulnerability can be exploited by a remote attacker who has already compromised the renderer process in Google Chrome. Exploitation occurs via a malicious HTML page, allowing the attacker to perform an out-of-bounds memory write, potentially leading to further code execution or system compromise within the renderer sandbox.
Mitigation is addressed in the stable channel update for Google Chrome desktop, as detailed in the Chrome Releases blog post at https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_31.html. Users should update to version 146.0.7680.178 or later. Additional technical details are available in the Chromium issue tracker at https://issues.chromium.org/issues/489791424.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-17787
Vulnerability Data
Integer overflow in ANGLE in Google Chrome on Windows prior to 146.0.7680.178 allowed a remote attacker who had compromised the renderer process to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: High)
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
SI-10 directly requires validation of all inputs, eliminating the assumption that client-supplied parameters remain immutable.
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 require server-side validation of all inputs instead of trusting client-supplied immutable parameters.
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 coding standards require server-side verification of client-supplied data, eliminating the root cause of external control of immutable parameters.
Security testing in development and acceptance will detect parameter tampering vulnerabilities before deployment.
Secure development lifecycle mandates input validation and integrity checks that directly prevent external tampering of assumed-immutable parameters.
Application security requirements explicitly call for validation of all inputs, including hidden fields, mitigating CWE-472.
Information access restriction can limit which parameters users may influence, providing a secondary layer of defense.