Cyber Resilience

CVE-2025-0436

Google Chrome ≤ 132.0.6834.83

Public PoC
Published
15 January 2025
Modified
21 April 2025
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.0040 33th percentile
Risk Priority 64 floored blend · peak EPSS

Summary

CVE-2025-0436 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 33th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

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-2025-0436 is an integer overflow vulnerability in the Skia graphics library used by Google Chrome prior to version 132.0.6834.83. The flaw enables potential heap corruption when rendering a crafted HTML page, as classified under CWE-472. Chromium rates its security severity as High, with 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).

A remote attacker can exploit this vulnerability by luring a user to visit a malicious website containing the crafted HTML page, requiring user interaction such as clicking a link but no special privileges. Successful exploitation could allow the attacker to achieve high-impact corruption of the heap, potentially leading to arbitrary code execution and full compromise of the browser's confidentiality, integrity, and availability.

Google's stable channel update for desktop, announced via the Chrome Releases blog, patches this issue in version 132.0.6834.83 and later. Additional technical details are documented in the associated Chromium issue tracker. Security practitioners should prioritize updating affected Chrome installations to mitigate the risk.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Integer overflow in Skia in Google Chrome prior to 132.0.6834.83 allowed a remote attacker to potentially exploit heap corruption 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-13841Same product: Google Chrome
CVE-2026-14387Same product: Google Chrome
CVE-2026-13938Same product: Google Chrome
CVE-2026-14389Same product: Google Chrome
CVE-2025-7656Same product: Google Chrome
CVE-2026-9911Same product: Google Chrome
CVE-2026-2649Same product: Google Chrome
CVE-2026-8577Same product: Google Chrome
CVE-2026-8532Same product: Google Chrome
CVE-2026-14086Same product: Google Chrome

Affected Assets

google
chrome
≤ 132.0.6834.83

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