CVE-2026-79112 in Chrome
Summary
by MITRE • 08/26/2026
Out of bounds read in Skia in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to read memory inside the sandbox via a crafted HTML page. (Chromium security severity: Low)
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 08/26/2026
The vulnerability identified as an out-of-bounds read within the Skia graphics library, present in versions of Google Chrome prior to 152.0.7977.65, represents a critical failure in memory safety boundaries during rendering operations. This flaw allows for unauthorized access to system memory that should remain isolated from untrusted web content. The root cause lies in the improper handling of array indices or buffer lengths within Skia's image processing routines, where input data derived from maliciously crafted HTML pages is not sufficiently validated against allocated memory limits. When a renderer process executes these operations with malformed inputs, it triggers a read operation that extends beyond the intended memory allocation, exposing adjacent heap structures to the attacker-controlled context.
From an operational perspective, this vulnerability requires specific preconditions to be successfully exploited. The threat actor must first achieve code execution within the browser's sandboxed renderer process, typically through other vulnerabilities such as cross-site scripting or remote code execution flaws in web content. Once inside the renderer, the attacker can construct a specially crafted HTML page containing malicious JavaScript that invokes Skia functions with precise parameters designed to trigger the out-of-bounds read condition. The success of this exploitation relies heavily on the ability to control the input data fed into the graphics library and to interpret the leaked memory contents accurately despite browser mitigations like Address Space Layout Randomization.
The security severity is classified as low by Chromium standards, primarily because the sandbox architecture provides significant protection against direct system compromise. However, an out-of-bounds read still poses a serious risk of information disclosure. By reading arbitrary memory locations, an attacker can potentially leak sensitive data such as cryptographic keys, session tokens, or internal browser structures that could facilitate further exploitation chains. This type of vulnerability aligns with CWE-125, which describes Out-of-Bounds Read errors where software reads past the end of a buffer. It also maps to MITRE ATT&CK technique T1083, File and Directory Discovery, as memory leakage can be used to enumerate system information or locate specific files for subsequent attacks.
Mitigation strategies focus on both immediate patching and long-term architectural improvements. The primary defense is the deployment of Chrome version 152.0.7977.65 or later, which includes patches that enforce stricter bounds checking within Skia's rendering pipeline. Developers should ensure automated update mechanisms are active to prevent exposure windows. For organizations managing large fleets, centralized patch management systems must be configured to prioritize security updates for browser components. Additionally, implementing Content Security Policy headers can help mitigate the initial compromise vector by restricting script execution sources, thereby reducing the likelihood of an attacker gaining renderer access in the first place. Continuous monitoring for anomalous memory usage patterns and regular penetration testing focusing on graphics library interactions are recommended practices to detect potential exploitation attempts early.