External risk intelligence

Google Chrome MHTML Sandbox Escape Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-17710

This vulnerability requires a remote attacker to have already compromised the renderer process of the web browser. As a client-side application component, it is not a network-facing service, API, or gateway, and it requires the user to interact with malicious content to trigger the vulnerability within the local client environment.

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

A vulnerability in Google Chrome's handling of certain web pages could allow an attacker to escape the browser's security sandbox, potentially impacting user data and system control if exploited. This issue affects users on Mac systems.

  • Attackers can bypass Chrome’s security.
  • It enables broader system compromise.
  • Verify if Mac Chrome users are affected.

Attack Path

How an attacker could exploit the issue

An attacker who has already compromised the browser's rendering process could trick a user into visiting a specially crafted webpage. This could allow them to break out of the browser's sandbox.

  • Requires renderer process compromise.
  • Triggered by a malicious HTML page.
  • Risk of sandbox escape.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, a remote attacker who has already compromised the renderer process could potentially escape the browser's sandbox by tricking a user into visiting a crafted HTML page. This could allow the attacker to affect system data, user data, and service behavior.

  • System data could be accessed.
  • User interaction with malicious content may trigger it.
  • Sensitive information disclosure and system compromise are possible.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts Google Chrome on Mac. System owners and security teams should collaborate to identify affected endpoints, determine business criticality and exposure, and assign ownership for remediation. Initial actions involve confirming Chrome's presence, assessing its reachability and impact, and locating the accountable team before planning a response.

  • Chrome owners should coordinate remediation efforts.
  • Verify Chrome browser presence and user impact.
  • Plan for updates during scheduled maintenance.

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 MHTML?

MHTML, or MIME HTML, is a web page archiving format used by Google Chrome to bundle the HTML code and its associated resources—like images or style sheets—into a single file. This component helps the browser save and display offline content correctly. In Chrome for Mac, this mechanism processes complex document structures, which is where the vulnerability exists.

How does CVE-2026-17710 enable a sandbox escape?

This vulnerability is classified as CWE-693, which concerns protection mechanism failures. It stems from an inappropriate implementation in the browser's MHTML handling. If an attacker triggers this flaw, they can break out of the 'sandbox'—the secure, isolated environment Chrome uses to contain web content—and gain the ability to perform actions outside of the browser's restricted boundaries.

Can I trigger this bug by simply visiting a regular website?

No. A successful attack requires two specific stages: first, the attacker must have already compromised the browser's renderer process. Second, they must successfully trick you into visiting a specially crafted, malicious HTML page designed to exploit the MHTML flaw. Simply browsing legitimate, trusted websites does not trigger this vulnerability.

How relevant is this threat to my environment?

Halo Surface Signal notes this is unlikely to impact your infrastructure directly because it is a client-side browser issue rather than a network-facing service or API. Because it requires a user to interact with malicious content, the risk is localized to the specific device and user, rather than being an exposed entry point for remote network-based exploitation.

What should I do if I use Google Chrome on Mac?

Your first step is to confirm the version of Chrome installed across your Mac fleet. Since this affects versions prior to 151.0.7922.72, you should coordinate with your IT or desktop support teams to identify outdated instances. Plan to deploy the latest browser update during your next maintenance cycle to ensure the security sandbox protections are properly reinforced.

References