EUVD-2026-105766
GHSA-g47f-9fxc-wggf
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitTrigger memory corruption in renderer
-
ExecutionExecute arbitrary code inside sandbox
-
ImpactAttempt chained sandbox escape
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, buffer size validation
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 the victim to use Google Chrome on Android at a version prior to 156.0.8078.47 and to actively open attacker-controlled crafted HTML content (UI:R) - e.g. navigating to a malicious site or opening a malicious link/ad. No authentication is required (PR:N) and the default browser configuration is sufficient; no special feature toggle is named in the description. The key limiting factors are the mandatory user interaction and, critically, that resulting code execution is confined to the renderer sandbox - full device compromise would additionally require a separate sandbox-escape vulnerability. |
| Impact | Signals conflict sharply and must be weighed carefully. The supplied 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 network-reachable, unauthenticated, low-complexity flaw needing only that a victim open a crafted HTML page - a classic drive-by profile. However, the description explicitly scopes the outcome to arbitrary code execution INSIDE the Chrome sandbox, and Google's own Chromium security team rated the severity Low. A sandbox-confined renderer compromise does not by itself yield host control; it would need to be chained with a separate sandbox-escape bug to become a full system takeover, which materially lowers real-world impact below what the 8.8 score implies. No EPSS score, no CISA KEV entry, and no public POC were provided, so there is no public exploit identified at time of analysis and no evidence of active exploitation. Net: patch promptly as part of routine Chrome updating because of the ubiquitous footprint and unauthenticated web vector, but this is not an emergency drop-everything issue - the sandbox confinement plus vendor 'Low' rating argue against the headline 8.8. Treat the CVSS/vendor-severity divergence as a genuine conflict to verify with the Chrome advisory rather than resolving it silently. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing malformed content that triggers the memory-corruption bug when rendered by Chrome on Android, and lures a victim into visiting it (UI:R). On visit, the attacker gains arbitrary code execution within the renderer sandbox; no public POC was provided, and converting this into device compromise would require an additional sandbox-escape primitive. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Memory corruption in Google Chrome for Android prior to 156.0.8078.47 allows a remote, unauthenticated attacker to potentially execute arbitrary code inside the browser sandbox when a victim opens a crafted HTML page. Exploitation requires user interaction (UI:R) - navigating to attacker-controlled content - and the resulting code execution is confined to the renderer sandbox, so full device compromise would require a separate sandbox-escape vulnerability. Signals conflict sharply: the CVSS 3.1 score is 8.8 while Google assigns Chromium security severity Low, and no public exploit code or CISA KEV entry was identified at time of analysis; a vendor patch is available in 156.0.8078.47.
RemediationAI
Vendor-released patch: upgrade Google Chrome for Android to 156.0.8078.47 or later, distributed through Google Play; confirm the installed build in Chrome settings and use managed Play Store or Android Enterprise policies to enforce the minimum version across fleets. The vendor advisory is at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html and the tracking issue is https://issues.chromium.org/issues/563812927. No documented feature toggle or configuration workaround is provided for this memory-corruption flaw; if immediate updating is not possible, constrain browsing to trusted destinations and block known-malicious URLs at the network or MTD layer, accepting that this reduces but does not eliminate exposure and may cause usability friction. Keep Android platform security patches current as a compensating control, since full device compromise from this bug would require a separate sandbox-escape vulnerability.
Affected VersionsENISA
Affected Packages
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 classified as CWE-119, improper restriction of operations within the bounds of a memory buffer, in Chrome's Mobile component on Android. A crafted HTML page triggers memory corruption in the browser's rendering path; with the CVSS vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, an unauthenticated remote attacker needs only that the victim load the page, after which the corruption can be shaped toward arbitrary code execution. Because Chrome's multi-process architecture places renderer code in a sandbox, the demonstrated impact is code execution inside that sandbox rather than at the Android OS level; escaping it would require chaining a second vulnerability. The gap between the 8.8 CVSS score and Google's Low Chromium severity likely reflects the mandatory user interaction and sandbox confinement, which materially reduce real-world risk compared with an unauthenticated, no-interaction renderer compromise.
Know when Chrome 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
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Remote crafted page, no auth, with required user interaction (UI:R); high impact reflects in-sandbox code execution, though real impact is sandbox-confined absent an escape.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Memory corruption in Mobile in Google Chrome on on Android prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Low)
Executive ViewAI
Google Chrome for Android versions prior to 156.0.8078.47 contain a memory-corruption flaw that could allow a remote attacker to execute code inside the browser sandbox when a user opens crafted HTML, affecting mobile employees who browse the web. Although the CVSS score is 8.8, Google rates the issue Low, no public exploit was identified at time of analysis, and exploitation requires user interaction and remains sandbox-confined, so leadership should treat this as a manageable but mandatory patch cycle rather than an emergency.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player
V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac
Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, a
The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, do
Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderb
Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi
An issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Conta
The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi
The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se
Use-after-free vulnerability in the BitmapData class in the ActionScript 3 (AS3) implementation in Adobe Flash Player 13
Exploit-DB