Executive brief
Google Chrome contains a missing authorization check in its FileSystem component that could allow an attacker with control of the browser's renderer process to bypass web origin policies. This could enable unauthorized access to files or data that should be restricted to specific websites. The vulnerability requires the renderer process to be already compromised, limiting its standalone impact.
Technical details
A missing authorization vulnerability exists in Chrome's FileSystem implementation prior to version 152.0.7977.75. The issue occurs when the renderer process—a sandboxed component responsible for displaying web pages—fails to properly enforce origin-based access controls on filesystem operations. An attacker who has already compromised the renderer process can craft a malicious HTML page to bypass web origin policy restrictions and access filesystem resources outside the intended scope. The vulnerability requires prior compromise of the renderer process, which itself typically requires code execution vulnerabilities or social engineering. A patch is available in Chrome 152.0.7977.75 and later.
Affected products
- Google Chrome prior to 152.0.7977.75
Timeline
- 2026-09-02: disclosed
- 2026-09-02: patched: Fix available in Chrome 152.0.7977.75