External risk intelligence

Chrome Improper Input Validation Vulnerability Allows Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-113084

This vulnerability affects a client-side web browser. While it requires the user to load a crafted HTML page, the vulnerability itself exists within the browser's local client implementation. It is not an internet-facing service, appliance, or gateway that is inherently exposed to the public internet for inbound connections in a server-side capacity.

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 security vulnerability has been identified in Google Chrome, related to how it handles permissions. This flaw could allow attackers to execute malicious code on a user's device through a specially designed webpage, potentially impacting user data and system integrity. The main concern is confirming whether our environments and users are exposed.

  • Flaw in browser permissions allows code execution.
  • High potential impact if user visits malicious site.
  • Confirm relevance and exposure to affected users.

Attack Path

How an attacker could exploit the issue

A remote attacker could trick a user into visiting a malicious webpage, which would then exploit an improper input validation flaw in Chrome's permissions system. This flaw could allow the attacker to execute code beyond the browser's security sandbox.

  • No specific entry conditions.
  • Triggered by visiting a crafted HTML page.
  • Risk of arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, a remote attacker could potentially execute arbitrary code outside the sandbox by tricking a user into visiting a crafted HTML page. This could affect the behavior of the browser service and any data accessible by the browser.

  • Arbitrary code execution outside sandbox.
  • Remote attacker via crafted HTML page.
  • Compromise of local browser data.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Chrome requires user interaction via a malicious HTML page, indicating that direct system exposure is unlikely for most organizations. The primary concern lies with end-user devices and how they interact with web content. System owners should first identify all endpoints running Chrome and assess user browsing habits. Coordination with IT support and end-user awareness training may be necessary.

  • Identify Chrome endpoints.
  • Verify user exposure to malicious pages.
  • Plan targeted user communication.

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

Google Chrome is a widely used web browser that serves as the primary interface for users to access and interact with internet content. It includes a security sandbox designed to isolate web page processing from the underlying operating system. This specific vulnerability affects how Chrome manages permissions, which are controls that limit what a website can access on your device, such as your camera, microphone, or local files.

What does improper input validation mean for this Chrome vulnerability?

Improper input validation, categorized as CWE-20, occurs when software fails to properly check the data it receives from an external source before using it. In this case, Chrome does not correctly verify the data related to its permission settings. Because the browser trusts this malformed data, it inadvertently allows the attacker to break out of the security sandbox and perform unauthorized actions on the host device.

How is this Chrome vulnerability triggered?

The flaw is triggered when a user visits a specifically crafted HTML page designed to exploit the permission validation error. It does not trigger simply by having the browser installed or running in the background. The attack requires active user interaction; navigating to a standard, benign website will not initiate this vulnerability.

Is my organization at high risk according to Halo Surface Signal?

Halo Surface Signal indicates that this vulnerability is very unlikely to pose a server-side risk. Because the flaw exists within the client-side browser implementation rather than an internet-facing server, appliance, or gateway, it does not provide an entry point for remote attackers to probe your network infrastructure directly. The risk is localized to the specific end-user devices where the browser is active.

Do I need to take immediate action if I run Chrome?

Yes. Since this issue allows for arbitrary code execution, you should prioritize updating your Chrome installation to version 156.0.8078.47 or later. Beyond applying the update, focus on identifying all endpoints in your environment where Chrome is used and consider reinforcing user awareness regarding the importance of only visiting trusted websites.

References