Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-113169 Overview
CVE-2026-113169 is a memory corruption vulnerability in the WebAppInstalls component of Google Chrome on Android. The flaw affects Chrome versions prior to 156.0.8078.47. A remote attacker can exploit the vulnerability by convincing a user to load a crafted HTML page, resulting in arbitrary code execution outside the browser sandbox. The vulnerability is classified under [CWE-119] (Improper Restriction of Operations within the Bounds of a Memory Buffer).
Critical Impact
Successful exploitation enables arbitrary code execution outside the Chrome sandbox on Android devices, giving attackers access to resources normally isolated from browser-rendered content.
Affected Products
- Google Chrome for Android prior to 156.0.8078.47
- Google Android (as the host platform for the affected Chrome builds)
- Any application embedding the vulnerable Chrome WebAppInstalls component
Discovery Timeline
- 2026-10-20 - CVE-2026-113169 published to the National Vulnerability Database (NVD)
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-113169
Vulnerability Analysis
The vulnerability resides in the WebAppInstalls subsystem of Chrome on Android. This component manages the installation flow for Progressive Web Apps (PWAs) and web app manifests. Memory corruption in this code path allows an attacker-controlled HTML page to influence memory structures used during installation handling.
Because the flaw permits code execution outside the renderer sandbox, an exploit bypasses one of Chrome's primary security boundaries. User interaction is required, consistent with the attack flow of triggering an install prompt or install-related API from a malicious page. The Chromium project rated the underlying bug as low severity, but the resulting sandbox escape elevates the practical risk.
Root Cause
The root cause is improper restriction of operations within the bounds of a memory buffer in WebAppInstalls. Memory corruption flaws in this class typically arise from out-of-bounds reads or writes, use-after-free conditions, or incorrect size calculations when parsing attacker-controlled input such as web app manifests, icons, or install metadata.
Attack Vector
Exploitation requires a user to visit or interact with a crafted HTML page served over the network. The attacker delivers the page through phishing, malvertising, or a compromised site. Upon interaction with web app install functionality, the crafted content triggers the memory corruption and executes code outside the sandbox. No prior authentication is required.
No verified public proof-of-concept code is available. For technical details, refer to Chromium Issue #562955271.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-113169
Indicators of Compromise
- Chrome for Android processes spawning child processes or accessing files outside expected sandbox directories
- Unexpected PWA or web app install events originating from untrusted domains
- Crashes in Chrome on Android with stack traces referencing WebAppInstalls or web app manifest parsing
- Outbound connections from Chrome-launched processes to attacker-controlled infrastructure following a browsing session
Detection Strategies
- Inventory Chrome for Android versions across managed mobile devices and flag any build earlier than 156.0.8078.47
- Correlate browser crash telemetry with recent navigation events to identify suspicious install-related triggers
- Monitor HTTP(S) traffic for pages hosting unusual manifest.json resources or scripting the Web App Install API from low-reputation domains
Monitoring Recommendations
- Enable mobile endpoint telemetry collection to capture Chrome process behavior and crash events
- Centralize browser and mobile OS logs in a SIEM for correlation with threat intelligence feeds
- Alert on anomalous activity following web app installation prompts, including unexpected background processes or file writes
How to Mitigate CVE-2026-113169
Immediate Actions Required
- Update Google Chrome on Android to version 156.0.8078.47 or later through the Google Play Store
- Enforce automatic Chrome updates via mobile device management (MDM) policy on managed Android fleets
- Communicate the risk to end users and advise caution with web app install prompts from unfamiliar sites
Patch Information
Google has released a fixed build of Chrome for Android starting at version 156.0.8078.47. Patch details are published in the Chrome Release Update. Tracking information is available in Chromium Issue #562955271.
Workarounds
- Restrict installation of web apps and PWAs through MDM policy where supported
- Block navigation to untrusted domains at the network perimeter or via DNS filtering
- Temporarily use an alternate browser on Android devices that cannot be patched immediately
# Verify Chrome for Android version on a managed device via adb
adb shell dumpsys package com.android.chrome | grep versionName
# Expected output should show versionName=156.0.8078.47 or higher
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

