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-113053 Overview
CVE-2026-113053 is a use-after-free vulnerability in the Cookies component of Google Chrome on Android versions prior to 156.0.8078.47. A remote attacker can execute arbitrary code inside the Chrome renderer sandbox by convincing a user to load a crafted HTML page. The flaw is classified under CWE-416: Use After Free and affects the browser's cookie handling logic.
Google rates the Chromium security severity as Low, but the National Vulnerability Database assigns a higher score due to the potential for arbitrary code execution following user interaction with attacker-controlled web content.
Critical Impact
Remote attackers can execute arbitrary code inside the Chrome sandbox on Android devices through a crafted HTML page, leading to potential browser compromise and follow-on sandbox escape chaining.
Affected Products
- Google Chrome for Android prior to version 156.0.8078.47
- Google Android devices running vulnerable Chrome builds
- Chromium-based mobile browsers sharing the affected cookie handling code
Discovery Timeline
- 2026-10-20 - CVE-2026-113053 published to the National Vulnerability Database
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-113053
Vulnerability Analysis
The vulnerability is a use-after-free (UAF) condition in Chrome's Cookies subsystem on Android. Use-after-free bugs occur when a program continues to reference heap memory after it has been freed. An attacker who controls the allocation layout can reclaim the freed memory with controlled data and hijack execution when the dangling pointer is dereferenced.
In this case, the dangling reference lives in cookie-handling code reachable from standard web content. A crafted HTML page can trigger the vulnerable code path during normal navigation or script execution. Exploitation requires user interaction, consistent with loading a malicious URL or embedded frame.
Successful exploitation yields arbitrary code execution inside the renderer sandbox. While the Chromium sandbox limits direct system impact, attackers routinely chain renderer UAFs with sandbox escapes to achieve full device compromise on Android.
Root Cause
The root cause is improper lifetime management of a cookie-related object. Chrome frees the object while another code path retains a pointer to it, then later dereferences that pointer. The condition maps directly to CWE-416.
Attack Vector
The attack vector is network-based with low complexity. An attacker hosts or injects a crafted HTML page. When a user on a vulnerable Chrome for Android build visits the page, the renderer processes attacker-controlled markup or scripting that triggers the UAF. No authentication is required.
Technical details are tracked in the Chromium Issue Tracker #40061291 and the Google Chrome Stable Update advisory.
Detection Methods for CVE-2026-113053
Indicators of Compromise
- Chrome for Android renderer processes crashing or terminating unexpectedly after visiting untrusted sites
- Unusual child process spawns from com.android.chrome not matching normal browsing patterns
- Outbound connections from mobile endpoints to recently registered or low-reputation domains serving HTML payloads
Detection Strategies
- Inventory installed Chrome versions on managed Android devices and flag builds below 156.0.8078.47
- Monitor mobile EDR telemetry for renderer crashes correlated with specific URLs or domains
- Correlate web proxy logs with crash telemetry to identify crafted HTML pages targeting the Cookies component
Monitoring Recommendations
- Enable mobile threat defense telemetry on Android fleet devices to capture browser process anomalies
- Ingest Chrome crash reports and browsing telemetry into a central data lake for correlation
- Track Chrome Releases blog advisories to identify emerging exploitation patterns
How to Mitigate CVE-2026-113053
Immediate Actions Required
- Update Chrome for Android to version 156.0.8078.47 or later through the Google Play Store
- Push mandatory browser updates via Mobile Device Management (MDM) to enforce patched versions across the fleet
- Audit Android devices for Chrome versions below the fixed build and quarantine non-compliant endpoints
Patch Information
Google released the fix in Chrome 156.0.8078.47 on the Stable channel. Reference the Google Chrome Stable Update advisory for the official release notes. Users should verify the installed version in chrome://version or Android app settings after applying updates.
Workarounds
- Restrict browsing to trusted sites via MDM policy until all devices receive the patched Chrome build
- Deploy mobile web filtering to block known malicious domains and newly registered infrastructure
- Disable JavaScript on untrusted sites through Chrome site settings where business workflows allow
# Verify Chrome for Android version via adb
adb shell dumpsys package com.android.chrome | grep versionName
# Expected output after patching:
# versionName=156.0.8078.47
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

