External risk intelligence

Chrome FileSystem Authorization Flaw Allows Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-121104

This vulnerability exists within the client-side Google Chrome browser and requires a user to be socially engineered into visiting a specifically crafted HTML page. It is not an internet-facing service, gateway, or reachable network application, but rather a client-side execution risk that is not exposed by design in common deployments.

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 security vulnerability in Google Chrome's FileSystem component. It could allow a malicious actor, through user interaction like clicking a link, to execute unauthorized code outside of the browser's secure environment. The primary concern is confirming if our environment is potentially exposed and understanding the relevance of this client-side risk.

  • Flaw lets malicious code run outside the browser.
  • User clicks a bad link to trigger the attack.
  • Confirm relevance and our exposure to this risk.

Attack Path

How an attacker could exploit the issue

A remote attacker could trick a user into visiting a malicious HTML page. This page could exploit an authorization flaw in Chrome's file system handling, allowing code to run outside the browser's normal security boundaries.

  • Attacker needs user to visit a link.
  • Flawed file system authorization.
  • Arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

A remote attacker could execute arbitrary code outside the browser's sandbox by tricking a user into visiting a malicious HTML page. This could affect sensitive information and system data when supported by the advisory.

  • Arbitrary code execution outside the sandbox.
  • Socially engineered user visits malicious page.
  • System data and sensitive information exposure.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability, affecting Google Chrome, necessitates action from teams responsible for end-user computing and browser management. The primary first step is to identify all instances of the affected browser version, assess their potential exposure through user interaction, and confirm ownership. Once identified and prioritized, a remediation plan, potentially involving coordinated updates, can be established.

  • End-user computing or browser owners.
  • Verify browser versions on endpoints.
  • Coordinate targeted user-facing updates.

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 Google Chrome's FileSystem component?

Google Chrome is a web browser used to navigate the internet. The FileSystem component is an internal mechanism that manages how the browser interacts with local files and data storage. It acts as an intermediary, ensuring that web pages can only access or modify files within strictly defined, secure boundaries to keep your computer safe from unauthorized data access.

How does CVE-2026-121104 work?

This vulnerability is classified as Incorrect Authorization (CWE-863). It means the browser fails to properly verify if an action requested by a web page is permitted. Because of this flaw, a malicious site can bypass security restrictions and run code on your computer, effectively escaping the browser's sandbox environment, which is the layer intended to isolate websites from your operating system.

Do I need to be tricked to trigger this bug?

Yes. This flaw requires social engineering, meaning an attacker must successfully convince you to visit a specially crafted web page. It does not trigger simply by having the software installed or by browsing legitimate sites. If you do not navigate to the malicious link, the vulnerable component remains dormant and cannot be exploited by the attacker.

Is this risk relevant to my network infrastructure?

According to Halo Surface Signal, this is a client-side execution risk rather than a classic internet-facing service or gateway vulnerability. It does not exist as a reachable network application that an attacker can scan for and compromise remotely. The risk is localized to end-user devices where a human user must be induced to participate.

When should I take action for CVE-2026-121104?

You should prioritize this if you manage end-user devices running Google Chrome. The first step is to audit your environment to identify systems running versions older than 157.0.8103.38. Once identified, coordinate with your team to roll out the official security update provided by the vendor, which closes the authorization gap and restores the integrity of the sandbox environment.

References