CVE-2026-87525 in Chrome
Summary
by MITRE • 09/09/2026
Out of bounds read in Chromoting in Google Chrome on on Windows prior to 153.0.8010.36 allowed a local attacker to read memory outside the sandbox via a local program. (Chromium security severity: High)
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 09/09/2026
The vulnerability identified as an out-of-bounds read within the Google Chrome Chromoting component represents a significant memory safety flaw that compromises the integrity of the browser's execution environment on Windows systems prior to version 153.0.8010.36. This specific defect is categorized under CWE-125, which describes Out-of-Bounds Read vulnerabilities where software reads data past the end or before the beginning of a buffer. In this context, the Chromoting component, responsible for remote desktop functionality and screen sharing features within Chrome, failed to properly validate memory access boundaries during its operation. This lack of rigorous boundary checking allows an attacker who has established local execution privileges on the target system to trigger malformed data processing that results in reading arbitrary memory locations outside the intended scope.
The operational impact of this vulnerability is particularly severe due to the sandboxing mechanisms inherent to modern web browsers like Google Chrome. Typically, browser processes are confined within a restricted environment known as the renderer or utility process sandbox, which limits their ability to interact with the underlying operating system and sensitive user data. However, because Chromoting operates with elevated privileges relative to standard rendering processes to facilitate screen capture and input redirection, it serves as a potential pivot point for privilege escalation attacks. By exploiting this out-of-bounds read, a local attacker can bypass these sandbox restrictions, effectively escaping the isolated environment to access memory regions that should remain inaccessible. This capability enables the extraction of sensitive information such as session cookies, authentication tokens, or cryptographic keys stored in browser memory, leading to potential account compromise and unauthorized access to user data.
From a threat intelligence perspective, this vulnerability aligns with ATT&CK technique T1059, Command and Scripting Interpreter, specifically when leveraged for local privilege escalation via sandbox escape. The exploitation path involves the attacker crafting specific inputs or triggering specific Chromoting states that cause the memory read operation to access protected regions. Once the attacker gains the ability to read arbitrary memory, they can potentially construct further exploits to achieve full system compromise, although this particular CVE focuses on the information disclosure aspect of escaping the sandbox boundary. The severity rating of High reflects the ease with which a local user could exploit this flaw and the significant security implications associated with breaking out of the browser's protective layers.
Mitigation for this vulnerability requires immediate action by updating Google Chrome to version 153.0.8010.36 or later on all affected Windows systems. This update includes patches that enforce stricter memory boundary checks within the Chromoting module, ensuring that any attempt to read from invalid addresses is intercepted and handled safely without exposing underlying system memory. In environments where automatic updates are not feasible, administrators should manually verify the installed version of Chrome across all endpoints and apply the patch through centralized management tools. Additionally, organizations should review their local security policies to ensure that only authorized users have administrative or significant execution privileges on workstations running browser software, thereby reducing the attack surface available for initial exploitation by malicious insiders or malware already present on the system.