External risk intelligence

Chrome Network Memory Corruption Vulnerability Allows Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-113342

The vulnerability exists in a web browser, which is designed to process arbitrary, untrusted content from the public internet. While it requires user interaction, browsers are inherently public-facing applications routinely exposed to external network traffic in standard deployments.

Memory Corruption

Halo Surface Signal: 4 out of 5 — 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 could allow attackers to execute unauthorized code by luring users to a malicious webpage. While the impact is rated as critical, further assessment is needed to determine if our specific environment and configurations are affected.

Corrupts browser memory, allowing code execution.
Critical severity, potential for remote compromise.
Confirm relevance and exposure to our systems.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by tricking a user into visiting a malicious webpage. This webpage contains specially crafted code that targets a memory corruption flaw within the browser's network handling. If successful, an attacker could execute their own code, potentially impacting other applications running on the user's system.

Requires user to visit a malicious page.
Exploits a network memory corruption flaw.
Allows arbitrary code execution outside sandbox.

Live Threat

Current exploitation, exposure, and threat context

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

Arbitrary code execution in browser.
Visiting a malicious HTML page.
Compromised system or data.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Google Chrome's Network component, allowing remote code execution via a crafted HTML page, likely impacts users who interact with untrusted web content. The primary responsibility for managing this risk falls to the teams overseeing end-user computing and browser deployments, potentially including IT infrastructure or endpoint management. The first critical step is to identify all instances of the affected Chrome version within the organization, assess their exposure and business criticality, and then initiate a coordinated remediation plan.

Ownership: Endpoint and Browser Management Teams.
Verify first: Browser version and exposure.
Action: Plan and deploy updates.

Supplementary metadata

CVSS vector

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.

Free EASM Trial See How Signal Works

Frequently asked questions

What is Google Chrome and its role in my system?

Google Chrome is a widely used web browser based on the Chromium open-source project. It functions as an interface for navigating the internet, handling complex tasks like parsing HTML, executing JavaScript, and managing network requests. This software acts as a primary bridge between your local computer and the web, making it a critical tool for daily operations that must securely manage data from untrusted sources.

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

This vulnerability is classified as CWE-119, which refers to improper restriction of operations within the bounds of a memory buffer. In plain terms, the browser's network component fails to safely handle data, allowing an attacker to overwrite adjacent memory. Because this happens in a way that escapes the browser's security sandbox, it can lead to arbitrary code execution, giving an attacker control over the underlying system.

How does an attacker trigger this Chrome vulnerability?

An attacker triggers this bug by luring a user to visit a specifically crafted HTML page. The vulnerability is tied to the way the browser's network component processes web content. Simply having the browser installed is not enough to trigger the flaw; it requires the active processing of malicious data. Consequently, browsing legitimate, trusted websites does not initiate the flaw.

Why is this Chrome vulnerability relevant to my environment?

According to Halo Surface Signal, this vulnerability is considered highly relevant because web browsers are designed to constantly process untrusted content from the public internet. Since browsers are inherently public-facing applications that must interact with external network traffic to function, any device running an outdated version of Chrome is exposed to potential remote compromise.

Do I need to update my Chrome browser immediately?

Yes, the first step is to identify all systems running versions of Chrome prior to 156.0.8078.47 and prioritize their updates. Since this flaw allows for code execution outside the browser's sandbox, it poses a significant risk to your system's integrity. Ensure your endpoint management teams are coordinating the deployment of the latest stable version to mitigate this threat.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.