External risk intelligence

Google Chrome Turbolev Memory Corruption Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-118305

This vulnerability affects a web browser client and requires a user to navigate to a specifically crafted HTML page to trigger the issue. Because it is a client-side consumer application and not a network-exposed service, listener, or gateway, it does not have a public internet-facing attack surface in common deployments.

Memory Corruption

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 memory corruption vulnerability in Google Chrome's Turbolev component could allow a remote attacker to execute arbitrary code outside the sandbox by tricking a user into visiting a malicious webpage. This could potentially impact users' devices if exploited.

  • Code could run outside browser limits.
  • Affects user devices via web browsing.
  • Confirm if Chrome users are impacted.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into visiting a malicious webpage containing crafted HTML. This page would then interact with a memory corruption vulnerability in Turbolev, a component within Google Chrome. If successful, this could allow the attacker to execute code beyond the browser's normal security boundaries.

  • User must visit a malicious page.
  • Vulnerability triggered by crafted HTML.
  • Risk of code execution outside sandbox.

Live Threat

Current exploitation, exposure, and threat context

Memory corruption in Turbolev, when triggered by a malicious HTML page, could allow an attacker to execute code outside the browser's sandbox.

  • Arbitrary code execution outside sandbox.
  • Triggered by crafted HTML page.
  • Remote code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects Google Chrome, specifically the Turbolev component. Owners of end-user workstations and devices running the affected browser version are likely responsible for remediation. The initial step involves identifying all endpoints with the vulnerable browser, confirming user exposure, and planning for updates during a suitable maintenance window to minimize operational disruption.

  • Own the issue: Endpoint owners.
  • Verify first: Browser reachability and exposure.
  • Action: Plan and deploy 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 the Turbolev component in Google Chrome?

Turbolev is a specific internal component within the Google Chrome browser architecture. While Chrome is a web browser used for accessing internet content, Turbolev handles specialized tasks related to memory management or processing operations. This vulnerability concerns how that component safely manages memory when interpreting web content.

What does memory corruption mean in CVE-2026-118305?

Memory corruption, classified as CWE-119, happens when a program inadvertently modifies or accesses memory areas it should not touch. In this CVE, a flaw in the Turbolev component allows a crafted HTML page to trigger this behavior, potentially letting unauthorized code run outside the browser's protected sandbox environment.

How is this vulnerability triggered?

An attacker must lure a user to visit a malicious webpage containing specifically crafted HTML. The bug is not triggered by simply having the browser installed or running in the background; it requires the active processing of the attacker's malicious web content within the affected version of Chrome.

Do I need to worry about this if I use Chrome internally?

Halo Surface Signal indicates this is a client-side browser issue rather than a network-exposed service. Because it requires user interaction—specifically navigating to a malicious page—it does not present the same risks as a public-facing server or gateway. The risk depends on whether users browse untrusted external websites.

When should I update my browser to address CVE-2026-118305?

You should prioritize updating Chrome to version 156.0.8078.73 or later as soon as your maintenance schedule allows. First, identify all devices in your environment running the affected software. Since this is a client-side issue, ensuring users are on the patched version is the primary way to remove the potential for this exploit.

References