Executive brief
Google Chrome's Network component in the renderer process is missing authorization checks that could allow a compromised renderer process to bypass web origin policy. An attacker who has already compromised the renderer (the process that executes web pages) could craft a malicious HTML page to circumvent security policies that protect data isolation between websites. This could lead to unauthorized access to cross-origin data and a breakdown in Chrome's security boundaries.
Technical details
This vulnerability is a missing authorization flaw in Chrome's Network component within the renderer process. The root cause is insufficient authorization checks that fail to enforce the web origin policy (Same-Origin Policy) when handling network requests from a compromised renderer. An attacker must first compromise the renderer process itself, typically through another vulnerability in the browser or JavaScript engine. Once the renderer is compromised, the attacker can craft a malicious HTML page to bypass origin checks and access data from other origins. The vulnerability was fixed in Chrome 152.0.7977.65, and patches are available to all users on Windows, Mac, and Linux platforms.
Affected products
- Google Chrome prior to 152.0.7977.65
Timeline
- 2026-08-25: disclosed
- 2026-08-25: patched: Fixed in Chrome 152.0.7977.65