Security Resilience

CVE-2026-5912

Google Chrome ≤ 147.0.7727.55

Published
08 April 2026
Modified
24 July 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 27th percentile
Risk Priority 63 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-5912 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 Transmitted Data Manipulation (T1565.002); ranked at the 27th 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-5912 is an integer overflow vulnerability (CWE-472) in the WebRTC component of Google Chrome prior to version 147.0.7727.55. The flaw enables a remote attacker to perform an out-of-bounds memory write by processing a 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 was published on 2026-04-08.

A remote attacker can exploit this vulnerability without authentication by luring a user to interact with a malicious site, such as by visiting a crafted HTML page. Successful exploitation allows arbitrary out-of-bounds memory writes, potentially resulting in high confidentiality, integrity, and availability impacts, including code execution or system compromise within the browser's sandbox.

Mitigation involves updating Google Chrome to version 147.0.7727.55 or later, as announced in the stable channel update for desktop at https://chromereleases.googleblog.com/2026/04/stable-channel-update-for-desktop.html. Additional technical details are documented in the Chromium issue tracker at https://issues.chromium.org/issues/486498791, where it is rated as Low severity by Chromium security standards.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Integer overflow in WebRTC in Google Chrome prior to 147.0.7727.55 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: Low)

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1565.002 Transmitted Data Manipulation Impact
Adversaries may alter data en route to storage or other systems in order to manipulate external outcomes or hide activity, thus threatening the integrity of the data.
T1606.001 Web Cookies Credential Access
Adversaries may forge web cookies that can be used to gain access to web applications or Internet services.
T1657 Financial Theft Impact
Adversaries may steal monetary resources from targets through extortion, social engineering, technical theft, or other methods aimed at their own financial gain at the expense of the availability of these resources for victims.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-7942Same product: Apple Macos
CVE-2026-14069Same product: Apple Macos
CVE-2026-10019Same product: Apple Macos
CVE-2026-13796Same product: Apple Macos
CVE-2026-5277Same product: Apple Macos
CVE-2026-7340Same product: Apple Macos
CVE-2026-5910Same product: Apple Macos
CVE-2026-10963Same product: Apple Macos
CVE-2026-5274Same product: Apple Macos
CVE-2026-10018Same product: Apple Macos

Affected Assets

google
chrome
≤ 147.0.7727.55

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
blocks

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.

finds

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

prevents

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

References