CVE-2026-113261 in Chromeinfo

Summary

by MITRE • 10/21/2026

Use after free in WebAppInstalls in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 10/21/2026

The vulnerability identified as a use-after-free error within the WebAppInstalls component of Google Chrome prior to version 156.0.8078.47 represents a critical memory management flaw that undermines the browser's sandboxing mechanisms. This specific class of vulnerabilities occurs when an application continues to reference a pointer after the memory it points to has been freed, leading to undefined behavior that can be exploited by malicious actors. In this instance, the defect resides in the logic governing how web applications are installed and managed within the Chromium engine, where references to objects were not properly invalidated or checked for validity before being accessed again during subsequent operations.

From a technical perspective, the root cause is classified under CWE-416, which denotes Use After Free conditions. These errors typically arise when an object's lifetime management fails to account for all active pointers referencing it. When the original memory block is deallocated but retained in use by another part of the program, subsequent read or write operations target invalid memory addresses. In the context of a web browser, this often involves DOM elements, JavaScript objects, or internal renderer structures that are manipulated via crafted HTML pages. The attacker constructs a webpage containing specific scripts and markup designed to trigger the premature deallocation of these resources while maintaining active references within other parts of the application state.

The operational impact of this vulnerability is severe because it allows for potential arbitrary code execution outside the browser's sandbox environment. Modern browsers rely heavily on process isolation and sandboxes to contain malicious activity, ensuring that even if a renderer process is compromised, the attacker cannot easily access sensitive system resources or user data. By exploiting this use-after-free flaw, an adversary can manipulate memory contents to achieve control over program flow, potentially bypassing these security boundaries. This capability enables the execution of arbitrary code with the privileges of the browser process, which could lead to full system compromise depending on the context and configuration of the victim's machine.

This exploitation vector aligns with ATT&CK technique T1203, specifically focusing on Exploitation for Client Execution, where attackers deliver malicious content through web-based vectors such as HTML pages or JavaScript files. The attack chain typically involves social engineering to lure a user into visiting a compromised site, followed by the automated execution of exploit code that leverages the memory corruption flaw. Once the sandbox is breached, subsequent stages may include privilege escalation, data exfiltration, or lateral movement within an enterprise network if the browser is used as an entry point for broader attacks.

Mitigation strategies primarily involve immediate patching to version 156.0.8078.47 or later, where Google has addressed the memory management issues in the WebAppInstalls module. Organizations should enforce automated update policies to ensure all endpoints are running patched versions of Chrome and Chromium-based browsers. Additionally, implementing strict content security policies can help mitigate some risks by restricting inline scripts and untrusted sources, although this does not directly prevent exploitation of low-level memory corruption flaws. Security teams should also monitor for indicators of compromise associated with browser exploit kits that target known vulnerabilities in web rendering engines to detect potential attempts at exploitation before they succeed.

Responsible

Chrome

Reservation

10/20/2026

Disclosure

10/21/2026

Moderation

accepted

EPSS

0.00437

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!