External risk intelligence

Chrome Canvas Memory Corruption Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-112992

The vulnerability exists within the client-side browser application (Google Chrome). While it requires a user to interact with crafted content, the attack surface is local to the end-user device rather than a public-facing network service, edge gateway, or server-side infrastructure. It does not represent a service deployed for external internet accessibility.

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 Canvas component presents a risk of arbitrary code execution if a user visits a malicious web page. While the severity is rated as critical, the main concern is to confirm whether this specific component is used in your environment and if related exposure exists.

  • Code could run outside the browser.
  • Affects users who browse malicious sites.
  • Confirm if this component is in use.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into visiting a malicious HTML page using a web browser. This page would trigger a memory corruption flaw in the browser's Canvas component, potentially allowing the attacker to execute their own code.

  • Requires user interaction with a web page.
  • Triggers memory corruption in Canvas.
  • Risk of arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

A memory corruption vulnerability in Chrome's Canvas component could allow a remote attacker to execute arbitrary code outside the sandbox. This could occur when a user visits a specially crafted HTML page, potentially impacting the confidentiality, integrity, and availability of the user's system.

  • User's system and data.
  • Visiting a malicious webpage.
  • Arbitrary code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts the client-side application, Google Chrome. Responsibility for triage and remediation typically lies with endpoint security or IT operations teams who manage user devices. The first practical move is to identify all Chrome instances, assess user exposure to malicious content, and prioritize affected users based on risk and criticality.

  • Endpoint security or IT operations ownership.
  • Verify user exposure to malicious content.
  • Plan user-facing remediation and 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's Canvas component?

Canvas is a feature within the Chrome browser that allows developers to render and manipulate graphics, animations, and visual elements directly on a webpage using scripts. Because it handles complex graphical data, it requires careful memory management to ensure that information processed by the browser remains secure and isolated from the rest of your system.

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

This vulnerability, classified as CWE-119, occurs when the software incorrectly handles data stored in its memory. In this specific case, an attacker can exploit the way the Canvas component processes information to overwrite parts of the browser's memory. This breach can allow the attacker to run unauthorized code on the machine, bypassing the browser's internal security boundaries.

How is this vulnerability triggered?

An attacker must trick a user into visiting a specially crafted HTML webpage that contains malicious instructions designed to exploit the Canvas component. Simply having the browser installed does not trigger the flaw; it requires active user interaction with a site built specifically to cause this memory error. Navigation to standard or trusted websites will not activate this bug.

Does this CVE affect my internet-facing servers?

According to Halo Surface Signal, this vulnerability is very unlikely to affect your internet-facing servers or edge gateways. It exists specifically within the client-side Google Chrome application installed on individual user devices. The risk is localized to the end-user's machine rather than your server-side infrastructure or public services.

What should I do if I run Google Chrome?

Since this is a client-side issue, your primary goal is to ensure all user devices are running a patched version of Google Chrome, specifically version 156.0.8078.47 or later. Coordinate with your IT or endpoint management teams to verify that browser updates are being deployed to all workstations and advise users to exercise caution when visiting untrusted or unknown websites.

References