External risk intelligence

Google Chrome WebAppInstalls Memory Corruption Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-113138

This vulnerability exists within the client-side browser engine (Google Chrome) and requires a user to navigate to a crafted HTML page. It is not an internet-facing service, gateway, or reachable network appliance, but rather a client-side application component. Exposure relies on client-side interaction rather than a public-facing network service.

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 security vulnerability in Google Chrome could allow an attacker to execute unauthorized code by luring a user to a malicious webpage. This memory corruption issue affects the WebAppInstalls component, potentially leading to broader system compromise if exploited. The primary concern is to confirm if our environment is exposed to this type of client-side attack vector.

  • Memory flaw in Chrome allows code execution.
  • User interaction needed; not an internet-facing risk.
  • Confirm relevance and exposure to client-side threats.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into visiting a malicious website, which then targets a memory corruption flaw in Chrome's WebAppInstalls feature. This could allow them to run unauthorized code on the user's device, potentially breaking out of the browser's security sandbox.

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

Live Threat

Current exploitation, exposure, and threat context

A memory corruption flaw in Google Chrome's WebAppInstalls feature, when interacting with a malicious HTML page, could allow an attacker to execute arbitrary code outside the browser's sandbox. This means an attacker could potentially compromise the user's system beyond the normal security boundaries of the browser.

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

Operational Fix

Recommended remediation, mitigation, and detection steps

Given this is a client-side vulnerability in Google Chrome, the primary responsibility likely lies with end-user device management and potentially application packaging teams. The first practical step is to identify which users or systems are running the vulnerable version and confirm if any business-critical activities are performed on those devices. Subsequently, the accountable owner, which could be IT support, endpoint management, or security operations, should be identified to plan for targeted updates or other risk reduction measures.

  • Own by endpoint management or IT support.
  • Verify affected user devices and business criticality.
  • Deploy targeted browser updates 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 the WebAppInstalls component in Google Chrome?

WebAppInstalls is a specialized feature within the Google Chrome browser engine responsible for managing, installing, and configuring Progressive Web Apps (PWAs). It handles the logic that allows websites to act like locally installed applications on your desktop or mobile device. By integrating web content into the operating system's interface, this component bridges the gap between traditional browser tabs and standalone software, but it must strictly manage system memory to remain secure.

What does memory corruption mean in the context of CVE-2026-113138?

This vulnerability falls under the weakness class CWE-119, which refers to improper restriction of operations within the bounds of a memory buffer. In this specific case, the browser fails to properly handle data processed by the WebAppInstalls component. An attacker can leverage this mistake to overwrite adjacent memory, allowing them to force the software to execute unauthorized instructions outside the secure sandbox environment.

How is this memory corruption vulnerability triggered?

The flaw is triggered when a user navigates to a specifically crafted HTML page designed to exploit the WebAppInstalls feature. Crucially, simply having the browser installed or running in the background does not trigger the bug. The attack requires active user interaction—specifically, the user must visit the malicious site for the exploit code to execute against the browser's memory.

Do I need to worry about this if my systems are internal?

According to Halo Surface Signal, this vulnerability is not an internet-facing network service or appliance. Because it resides in a client-side browser engine, the risk is tied to user behavior rather than network exposure. Even on internal systems, the threat remains if a user on that device navigates to a malicious webpage, as the browser itself becomes the entry point for the attack.

When should I update my Google Chrome browser?

You should update to version 156.0.8078.47 or later as soon as possible. Because this flaw allows for code execution outside the browser's sandbox, it poses a high risk to system integrity. Coordinate with your endpoint management or IT support teams to ensure this update is pushed to all devices, prioritizing systems that frequently access external web content.

References