Cyber Resilience

CVE-2026-5274

Google Chrome ≤ 146.0.7680.177

Published
01 April 2026
Modified
01 April 2026
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0034 26th percentile
Risk Priority 63 floored blend · peak EPSS

Summary

CVE-2026-5274 is a high-severity External Control of Assumed-Immutable Web Parameter (CWE-472) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 26th 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-5274 is an integer overflow vulnerability in the Codecs component of Google Chrome versions prior to 146.0.7680.178. The flaw, classified under CWE-472, enables a remote attacker to perform arbitrary read and write operations through a specially crafted HTML page. It carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and is rated High severity by Chromium security.

A remote attacker can exploit this vulnerability by tricking a user into visiting a malicious website hosting the crafted HTML page, as it requires user interaction but no special privileges. Successful exploitation grants arbitrary read/write capabilities, potentially allowing full compromise of the affected browser process with high impacts on confidentiality, integrity, and availability.

Mitigation is provided in Google Chrome 146.0.7680.178 and later versions, as detailed in the Chrome stable channel update release notes at https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_31.html and the associated Chromium issue tracker at https://issues.chromium.org/issues/488596746. Security practitioners should ensure users update to the patched version promptly.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Integer overflow in Codecs in Google Chrome prior to 146.0.7680.178 allowed a remote attacker to perform arbitrary read/write via a crafted HTML page. (Chromium security severity: High)

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-9998Same product: Apple Macos
CVE-2026-14069Same product: Apple Macos
CVE-2026-10987Same product: Apple Macos
CVE-2026-7969Same product: Apple Macos
CVE-2026-13801Same product: Apple Macos
CVE-2026-10015Same product: Apple Macos
CVE-2026-5859Same product: Apple Macos
CVE-2026-5910Same product: Apple Macos
CVE-2025-10891Same product: Apple Macos
CVE-2026-9968Same product: Apple Macos

Affected Assets

google
chrome
≤ 146.0.7680.177

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.

PR.PS-06 mostly match
prevents

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.

prevents

Secure coding standards require server-side verification of client-supplied data, eliminating the root cause of external control of immutable parameters.

finds

Security testing in development and acceptance will detect parameter tampering vulnerabilities before deployment.

prevents

Secure development lifecycle mandates input validation and integrity checks that directly prevent external tampering of assumed-immutable parameters.

prevents

Application security requirements explicitly call for validation of all inputs, including hidden fields, mitigating CWE-472.

none

Information access restriction can limit which parameters users may influence, providing a secondary layer of defense.

References