External risk intelligence

Google Chrome Code Execution via Crafted HTML Page

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-118355

This vulnerability affects a web browser client. Exploitation requires a user to navigate to a specifically crafted HTML page. While the vector is network-based, the vulnerability is client-side and does not involve a service or infrastructure typically exposed on the public internet as a reachable endpoint.

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 in Google Chrome could allow an attacker to execute code outside the browser's secure sandbox by luring a user to a malicious webpage. This could potentially lead to broader system compromise if exploited. The main concern is confirming relevance and exposure to this type of client-side threat.

  • Malicious websites can risk user code execution.
  • User interaction is required for exploitation.
  • Verify browser usage and user awareness.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into visiting a malicious webpage. This page would contain specially crafted code that exploits a flaw in how Chrome handles input. If successful, this could allow the attacker to run their own code on the user's computer, potentially bypassing security measures.

  • Requires user to visit a malicious page.
  • Triggered by crafted HTML and input validation.
  • Risk of arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an attacker to execute arbitrary code on a user's system when they visit a malicious website, bypassing the browser's security sandbox.

  • Arbitrary code execution on user systems.
  • User visits a crafted HTML page.
  • Compromise of user's device and data.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Google Chrome requires a user to interact with a malicious HTML page, making client-side security teams and endpoint management responsible for initial triage. The first step is to identify Chrome installations, assess user exposure to the internet, and prioritize remediation for critical or highly exposed systems.

  • Endpoint security teams own remediation.
  • Verify user exposure and business criticality.
  • Plan phased deployments or user guidance.

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 this vulnerability?

Google Chrome is a web browser used to access the internet. It functions as a client-side application that renders HTML pages and executes web-based scripts. The browser employs a security sandbox to isolate website content from your underlying operating system, preventing malicious code from gaining unauthorized control over your device.

What does improper input validation mean for CVE-2026-118355?

This vulnerability is classified as CWE-20, which occurs when a program receives data but fails to verify if it is safe before processing it. In this case, Chrome incorrectly handles specifically crafted HTML content. This flaw allows the malicious code to break out of the browser's sandbox and run commands directly on your computer.

How is this vulnerability triggered by an attacker?

An attacker must successfully lure a user into visiting a malicious website containing the crafted HTML. The bug is not triggered by simply having the browser installed or running; it requires the active rendering of the specific malicious page. Standard, non-malicious web browsing does not trigger this vulnerability.

Why does Halo Surface Signal label this as very unlikely?

Halo Surface Signal notes that this is a client-side vulnerability rather than a server-side threat. While the attack is network-delivered via a website, it does not target infrastructure or open ports. Because the threat is localized to the end-user's browser experience, it lacks the typical characteristics of publicly reachable, high-risk infrastructure.

What is the recommended first step for teams managing this software?

The priority is to identify systems running older versions of Chrome that are susceptible to this flaw. Since the attack requires a user to navigate to a malicious page, focus your efforts on updating browsers across your fleet to the latest patched version. This minimizes the risk of code execution if a user accidentally visits a compromised site.

References