External risk intelligence

Google Chrome Remote Code Execution via Crafted HTML Page

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-113328

This vulnerability affects a client-side web browser. While it requires a remote attacker to provide a crafted HTML page, the attack surface is the end-user's local browser instance rather than an internet-facing service, API, or infrastructure component. It does not represent a public-facing deployment of a server or gateway.

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 critical vulnerability in Google Chrome could allow a remote attacker to execute malicious code on a user's device through a specially crafted webpage. While this issue requires user interaction, its potential for code execution outside the browser's secure environment warrants attention to understand its relevance to our organization.

  • Attackers could run harmful code via malicious websites.
  • Critical code execution risk in widely used browser.
  • Confirm if Chrome is used and user exposure.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into visiting a malicious HTML page. This page would exploit a flaw in how the browser handles input, allowing the attacker to run code on the user's computer outside of the browser's safe environment.

  • No special access needed.
  • Malicious HTML page.
  • Arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

Improper input validation in Privacy in Google Chrome could allow a remote attacker to execute arbitrary code outside the sandbox when a user visits a malicious HTML page. This could impact the confidentiality and integrity of user data and the availability of the browsing service.

  • User's browser data and system.
  • Visiting a malicious HTML page.
  • Arbitrary code execution and data compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Google Chrome's privacy features requires identifying all user-facing Chrome instances. The first practical step is to confirm user impact, especially for users interacting with untrusted web content, and then coordinate with endpoint management or security teams to plan remediation, potentially through vendor updates.

  • Browser owners should manage this issue.
  • Verify user exposure to malicious HTML.
  • Plan for controlled browser 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 in the context of CVE-2026-113328?

Google Chrome is a widely used web browser that processes HTML, CSS, and JavaScript to render websites. This vulnerability specifically impacts the Privacy component within the browser, which is designed to manage data protections and secure user interactions while browsing the internet.

How does this vulnerability work in simple terms?

This issue is classified as improper input validation (CWE-20). In plain English, the browser fails to properly check or sanitize certain data provided by a website. Because of this oversight, a crafted HTML page can bypass the browser's sandbox—a security boundary meant to keep web content isolated—potentially allowing malicious code to run on the underlying system.

Do I need to be logged into a site for this to trigger?

No, you do not need to be authenticated or perform specific actions like logging in. The trigger requires only that a user visits a malicious HTML page. However, simply having Chrome installed or open without navigating to a compromised or untrusted webpage does not trigger the vulnerability.

Is my organization at high risk from this CVE?

According to Halo Surface Signal, this risk is very unlikely to affect organizational infrastructure. Because this is a client-side browser issue, it does not involve internet-facing services or gateways. The risk is localized to the end-user's device and their specific browsing habits rather than your network servers.

What is the best way to respond to this browser threat?

The most effective response is to ensure Chrome is updated to version 156.0.8078.47 or later. Since the flaw involves user interaction with untrusted content, coordinate with your endpoint management teams to confirm that browser updates are deployed across your fleet and verify that users are running the patched version.

References