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-113166 Overview
CVE-2026-113166 is a memory corruption vulnerability in the History component of Google Chrome on Android. The flaw affects Chrome versions prior to 156.0.8078.47 and allows a remote attacker to execute arbitrary code inside the browser sandbox. Exploitation requires the victim to load a crafted HTML page. Google classifies the Chromium security severity as Medium, while NVD rates the issue High based on CVSS impact metrics. The weakness is tracked under CWE-119 (improper restriction of operations within the bounds of a memory buffer).
Critical Impact
Successful exploitation enables arbitrary code execution inside the Chrome renderer sandbox on Android devices through a single crafted web page.
Affected Products
- Google Chrome for Android prior to 156.0.8078.47
- Google Android (as the host platform for the vulnerable Chrome build)
- Chromium-based browser components bundled with Chrome on Android
Discovery Timeline
- 2026-10-20 - CVE-2026-113166 published to the National Vulnerability Database
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-113166
Vulnerability Analysis
The vulnerability resides in the History component of Chrome on Android. A crafted HTML page triggers memory corruption during history-related operations. An attacker who controls the page content can corrupt in-process memory structures and redirect execution. Because the issue is confined to the renderer process, code execution occurs inside the Chrome sandbox rather than at the OS level. A separate sandbox escape would be required to achieve full device compromise. The flaw requires user interaction, specifically that the target browses to or is redirected to an attacker-controlled page.
Root Cause
The root cause is improper restriction of operations within the bounds of a memory buffer, categorized as [CWE-119]. The History subsystem fails to correctly validate memory bounds while processing attacker-influenced data from a crafted document. The specific defect is tracked in the Chromium Issue Tracker Entry, which remains access-restricted pending broader patch adoption.
Attack Vector
Exploitation is network-based and requires no authentication. A victim must open a malicious HTML page or an attacker-controlled frame embedded in a legitimate site. Phishing, malvertising, and compromised third-party content are plausible delivery channels. Once the renderer processes the crafted page, the memory corruption primitive can be leveraged to execute arbitrary code inside the sandbox context on Android. See the Google Chrome Stable Update for Google's advisory language.
No verified proof-of-concept code is publicly available. The vulnerability mechanism is described in prose because no sanitized exploit sample has been published.
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-113166
Indicators of Compromise
- Android devices running Chrome versions earlier than 156.0.8078.47 after the patch release window
- Unexpected renderer process crashes on Android with signatures referencing the History component
- Outbound connections from mobile endpoints to newly registered or low-reputation domains that served HTML content immediately before a crash
Detection Strategies
- Inventory installed Chrome versions across managed Android fleets and flag any build below 156.0.8078.47
- Correlate Android crash telemetry with browsing history to identify renderer failures tied to specific URLs
- Use network inspection to identify HTML payloads with abnormal history or navigation API usage patterns
Monitoring Recommendations
- Monitor mobile device management (MDM) compliance reports for Chrome patch status on Android
- Track browser crash telemetry forwarded to centralized logging and alert on repeated renderer crashes per device
- Watch threat intelligence feeds for weaponized exploits targeting Chrome History memory corruption on Android
How to Mitigate CVE-2026-113166
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 on managed Android devices via MDM policy
- Instruct users to avoid untrusted links until patch deployment is verified across the fleet
Patch Information
Google released the fix in Chrome 156.0.8078.47 for Android. The update is distributed through the Google Play Store and documented in the Google Chrome Stable Update advisory. Administrators managing Android devices should confirm the installed Chrome build using MDM reporting after rollout.
Workarounds
- Restrict browsing to trusted sites until the Chrome update is confirmed on each device
- Deploy content filtering to block known malicious domains and newly registered domains hosting unsolicited HTML content
- Use alternative hardened browsers on high-risk Android devices until patch deployment completes
# Verify installed Chrome version on an Android device via adb
adb shell dumpsys package com.android.chrome | grep versionName
# Expected output after patch:
# versionName=156.0.8078.47 (or later)
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

