CVE-2026-113047 in Chrome
Summary
by MITRE • 10/21/2026
Memory corruption in BrowserTag in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially 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 • 10/21/2026
The vulnerability identified as a memory corruption issue within the BrowserTag component of Google Chrome prior to version 156.0.8078.47 represents a significant breach in the browser's isolation mechanisms, despite being classified with low severity by Chromium security teams. This flaw resides in a specific module responsible for managing tab-related state and interactions, where improper handling of memory allocation or deallocation leads to undefined behavior when processing maliciously crafted HTML content. The core technical failure involves an out-of-bounds read condition that allows data from adjacent memory regions to be accessed beyond the intended boundaries of allocated buffers. This type of error typically arises from a lack of rigorous bounds checking during array indexing operations or pointer arithmetic within the BrowserTag logic, enabling an attacker to extract sensitive information stored in nearby memory locations without triggering immediate application crashes or detection mechanisms.
From an operational perspective, this vulnerability poses a risk primarily through remote exploitation vectors where users are tricked into visiting specially crafted web pages hosted by malicious actors. Although the severity is rated as low, indicating that successful exploitation may be difficult or require specific conditions to achieve meaningful impact, the potential for information disclosure remains critical in the context of browser security models. The primary consequence is the ability of a remote attacker to read memory inside the sandbox environment surrounding the renderer process. This capability undermines the fundamental principle of least privilege and isolation that modern browsers enforce between different tabs and origins. By leaking data from within the sandbox, an attacker could potentially access sensitive user information such as session cookies, authentication tokens, or other private data stored in browser memory, which could facilitate further attacks like cross-site request forgery or account takeover if combined with additional vulnerabilities.
This incident aligns closely with Common Weakness Enumeration category CWE-125, which describes out-of-bounds read errors that allow attackers to access unintended memory regions. In the context of attack frameworks such as MITRE ATT&CK, this vulnerability facilitates techniques related to Collection and Credential Access, specifically leveraging browser-based attacks to harvest sensitive information from victim systems. The exploitation path typically involves social engineering tactics where users are directed to malicious sites via phishing emails or compromised advertisements that host the exploit code within embedded HTML structures. Once executed, the flaw allows the attacker's script to perform memory reads that bypass standard security controls designed to prevent cross-origin data leakage.
Mitigation strategies for this vulnerability focus primarily on timely patching and defense-in-depth practices. Users must update Google Chrome to version 156.0.8078.47 or later, where the underlying logic in BrowserTag has been corrected to enforce strict bounds checking before accessing memory regions. For organizations managing large fleets of devices, automated deployment tools should be utilized to ensure rapid distribution of this security patch across all endpoints. Additionally, implementing browser hardening policies such as disabling JavaScript execution on untrusted sites or using extensions that restrict access to sensitive APIs can provide an additional layer of protection against exploitation attempts. Security teams should also monitor for indicators of compromise related to unusual memory usage patterns in Chrome processes and ensure that endpoint detection systems are configured to flag potential exploit activity associated with known browser vulnerabilities.