External risk intelligence

Chrome FileSystem Authorization Bypass Allows Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-125347

This vulnerability is a client-side issue within a web browser, requiring a user to be socially engineered into visiting a crafted HTML page. It is not a service, gateway, or internet-facing infrastructure component designed to be reachable from the internet, but rather relies on end-user interaction with client software.

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a high-severity vulnerability identified in Google Chrome's FileSystem component. The issue allows attackers to execute code outside the browser's secure sandbox through a malicious HTML page, requiring user interaction via social engineering. While the technical severity is high, the reliance on user action means the immediate risk to widespread systems may be limited.

  • Browser flaw allows code execution outside sandbox.
  • High severity, relies on user interaction.
  • Confirm relevance to your user base.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into visiting a malicious webpage. This page would then exploit a flaw in the browser's file system handling to run code outside the browser's secure sandbox. This could allow the attacker to take control of the user's computer.

  • User visits a malicious webpage.
  • Crafted HTML page triggers vulnerability.
  • Arbitrary code execution outside sandbox.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an attacker to execute code outside the browser's sandbox when a user visits a malicious webpage, potentially affecting the user's system data.

  • System data could be affected.
  • Via a crafted HTML page and social engineering.
  • Arbitrary code execution outside the sandbox.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Google Chrome requires a user to be socially engineered into visiting a malicious HTML page, making it a client-side issue. The first practical step is for the security team to identify all endpoints running the affected browser version, confirm if any are business-critical or exposed to social engineering risks, and then coordinate with Chrome's owner or end-users for remediation.

  • Security and Endpoint Owners
  • Verify Chrome browser reachability.
  • Plan user-driven remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the FileSystem component in Google Chrome?

The FileSystem component is a browser subsystem that manages how web applications interact with local files on your computer. It provides a structured way for websites to read or write data while operating within the browser's security sandbox. In this context, it manages specific permissions for file access, which is where the flaw exists.

What does CVE-2026-125347 mean by incorrect authorization?

This vulnerability is classified as CWE-863, which means the software fails to properly verify if a user or action has the required permissions to perform a specific task. In this case, the browser mistakenly allows a web page to bypass security checks, letting it interact with parts of your system it should be blocked from accessing.

How is this vulnerability triggered?

An attacker must successfully use social engineering to trick a user into visiting a specifically crafted HTML page. Simply having the browser installed or visiting legitimate websites does not trigger this flaw. The code execution only occurs if the user interacts with the malicious content provided by the attacker.

Is my system at risk if I use Chrome?

Halo Surface Signal notes that this is a client-side issue, not a service or internet-facing infrastructure component. Because it requires user interaction rather than being an automated network attack, the risk is primarily focused on the end-user's device rather than direct server or gateway exposure.

What should I do if I am running affected versions of Chrome?

First, identify which endpoints in your environment are running versions prior to 157.0.8103.50. Since this is a browser update, ensure that the standard patch management process for end-user software is prioritized. Coordinate with users or IT support to ensure the browser is updated to the latest stable version to close the security gap.

References