Skip to main content

Google Chrome EUVDEUVD-2026-105729

| CVE-2026-113156 HIGH
Use After Free (CWE-416)
2026-10-20 chrome-cve-admin@google.com GHSA-4739-h7q3-q5w4
8.8
CVSS 3.1 · Vendor: google
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Lure victim to crafted HTML page
  2. Exploit
    Page triggers use-after-free in Messages
  3. Execution
    Reclaim freed memory with attacker data
  4. Impact
    Execute arbitrary code in renderer sandbox

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires a victim running Google Chrome on Android before version 156.0.8078.47 to actively open or load an attacker-controlled crafted HTML page (UI:R), which triggers the use-after-free in the Messages component. No authentication or prior privileges are needed (PR:N). The key limiting factor is that resulting code execution is confined to the renderer sandbox (S:U, vendor 'Low' severity) - absent a separate sandbox-escape vulnerability, the attacker does not gain control of the underlying Android device or data outside the renderer. Required user interaction and the availability of the vendor patch further reduce realistic exposure.

Impact

Signals are mixed and require careful reading. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) describes a remotely reachable, low-complexity flaw needing only that a victim open a crafted HTML page, which on paper is high-priority. However, the Chromium team assigned this a security severity of 'Low', and the description explicitly states code execution is confined 'inside the sandbox' with no scope change (S:U) - meaning no sandbox escape or host compromise is claimed. This is a direct conflict: the CVSS C:H/I:H/A:H rating treats renderer-process compromise as full high impact, while the vendor's 'Low' rating and the sandbox-containment language indicate real-world impact is constrained to the renderer process and typically requires chaining with a separate sandbox-escape bug to become dangerous. No EPSS score, CISA KEV listing, SSVC decision, or POC indicator was provided in the input; there is no public exploit identified at time of analysis and no evidence of active exploitation. Net assessment: patch promptly as part of normal Chrome update hygiene, but this is more of a high-CVSS-but-moderate-real-risk issue than an emergency - a sandboxed, user-interaction-dependent UAF with a vendor 'Low' rating and no exploitation signals.

Exploit ScenarioDerived

A remote attacker hosts or compromises a web page containing specially crafted content that triggers the use-after-free in the Messages component when a victim running a vulnerable Chrome on Android (prior to 156.0.8078.47) visits it. Successful exploitation yields arbitrary code execution confined to the renderer sandbox, not the host device. No public exploit code was identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

Use-after-free in Google Chrome for Android prior to 156.0.8078.47 lets a remote attacker potentially execute code inside the renderer sandbox when a victim loads a crafted HTML page. Exploitation is unauthenticated (PR:N) but requires the user to open attacker-controlled content (UI:R), and the resulting code execution stays confined to Chrome's sandbox - consistent with the vendor's 'Low' Chromium severity rating - so meaningful compromise of the Android device would require chaining a separate sandbox escape. Google has released a fixed build and no public exploit code has been identified at time of analysis, though NVD's base score of 8.8 is materially higher than our assessed vector (C:L/I:L/A:L) because it does not account for sandbox confinement.

RemediationAI

Vendor-released patch: Chrome 156.0.8078.47 for Android. Update through Google Play (or your managed-app distribution channel) and verify the installed build under Chrome > Settings > About Chrome; because Chrome's update mechanism is staged, confirm the version string rather than assuming an automatic update landed. Where immediate updating is not possible, reduce exposure by restricting browsing of untrusted or unsolicited HTML content, keeping Google Safe Browsing/Enhanced Protection enabled, and - for managed fleets - using enterprise policy to block outdated Chrome versions from accessing corporate resources until they report 156.0.8078.47; the trade-off is that blocking outdated clients interrupts user access, and disabling JavaScript or Messages-related features would shrink the trigger surface but break legitimate functionality and is not a substitute for patching. No vendor workaround beyond upgrading is documented in the available references, and the sandbox confinement noted by the vendor lowers - but does not eliminate - the urgency of patching. Advisory: https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html.

Affected VersionsENISA

Chrome 156.0.8078.47 <156.0.8078.47

Affected Packages

euvd chrome fix: 156.0.8078.47

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a classic CWE-416 use-after-free in Chrome's Messages component on Android. In a use-after-free, an object is deallocated while a stale pointer to it is still reachable; if the attacker can influence allocations after the free (spraying crafted HTML and JavaScript-driven heap activity), the reclaimed memory can be repurposed so that subsequent use of the dangling reference yields attacker-influenced data or control flow within the renderer process. Because Chrome renders untrusted web content in a heavily sandboxed, site-isolated renderer, the primitive lands inside the sandbox boundary rather than on the Android device itself - which is exactly why the Chromium team rated this 'Low' while an unadjusted CVSS vector scores 8.8 (AV:N/AC:L/PR:N/UI:R/C:H/I:H/A:H). The CPE data in the input is limited to the EUVD version range, but the affected surface is specifically the Android build of Chrome before 156.0.8078.47; the fix is referenced in the Chrome stable channel release and Chromium issue 553253820, indicating a memory-lifetime correction in the Messages code path.

Know when Android gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (google) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 6.3 MEDIUM

Remote, low-complexity, no-auth drive-by needing UI:R; impacts set to L and S:U because code execution is contained within the renderer sandbox per the vendor's 'Low' rating.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
CVSS changed
Oct 20, 2026 - 23:23 NVD
8.8 (HIGH)
Patch available
Oct 20, 2026 - 23:20 EUVD
CVE Published
Oct 20, 2026 - 22:19 cve.org
HIGH 8.8

DescriptionCVE.org

Use after free in Messages in Google Chrome on on Android prior to 156.0.8078.47 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Low)

Executive ViewAI

Why It Matters

Google Chrome for Android versions prior to 156.0.8078.47 contain a memory-safety flaw that could let a malicious web page run code inside Chrome's renderer sandbox, affecting any employee who browses the web on an Android device - a population that in most organizations is large and largely unmanaged. Because the impact is contained by the sandbox and requires the user to open attacker-controlled content, successful device compromise would need a second, separate exploit, and no public exploit code has been identified at time of analysis. Leadership should treat this as a patch-cadence and mobile-fleet-visibility issue rather than an emergency, while confirming that Android devices under management are actually receiving Chrome updates.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 68% exploitable
Prevalence
Ubiquitous
Google Chrome on Android is among the most widely deployed mobile browsers
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
Medium

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

CVE-2015-3105 CRITICAL POC
10.0 Jun 10

Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466

CVE-2015-3864 CRITICAL POC
10.0 Oct 01

Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A

CVE-2013-4710 CRITICAL POC
9.3 Mar 03

Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp

CVE-2015-1538 CRITICAL POC
10.0 Oct 01

Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef

CVE-2024-21633 HIGH POC
7.8 Jan 03

Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK

CVE-2017-13156 HIGH POC
7.8 Dec 06

An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability

CVE-2016-2107 MEDIUM POC
5.9 May 05

The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a

CVE-2015-3106 CRITICAL POC
10.0 Jun 10

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows

CVE-2015-3107 CRITICAL POC
10.0 Jun 10

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows

CVE-2013-4787 CRITICAL POC
9.3 Jul 09

Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows

CVE-2014-7911 HIGH
7.2 Dec 15

luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.

CVE-2016-0801 CRITICAL POC
9.8 Feb 07

The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy