EUVD-2026-105486
GHSA-mrm6-w8j4-8xxh
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
DeliveryMalformed content reaches compositing component
-
ExploitTrigger memory corruption (CWE-119)
-
ExecutionExecute arbitrary code in renderer sandbox
-
ImpactChain sandbox escape for host impact
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 open a crafted HTML page in a vulnerable Google Chrome desktop build prior to 156.0.8078.47 - no authentication is needed (PR:N) but user interaction is mandatory (UI:R), so the attack is not fully drive-by-automatic and depends on social engineering or malicious/compromised web content. The specific trigger is malformed content processed by Chrome's Compositing component. A key LIMITING factor is that successful code execution is confined to the renderer sandbox; achieving host compromise requires chaining a separate sandbox-escape vulnerability. No special non-default configuration is required - standard Chrome browsing is sufficient. |
| Impact | Signals conflict and must be weighed carefully. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U, C:H/I:H/A:H → 8.8 High) describes a network-reachable, unauthenticated, low-complexity flaw needing only that a victim open a page. However, Google/Chromium labels this 'Medium' severity, and the description explicitly states the attacker executes arbitrary code 'inside the sandbox' - i.e. within the renderer process, NOT a full host compromise. This contained impact is why the vendor's internal rating is lower than the mechanically-derived 8.8; realistic host takeover would require chaining this with a separate sandbox-escape bug. No EPSS score was supplied, the CVE is not in CISA KEV, and no public exploit is referenced, so there is no evidence of active or imminent exploitation. Net: this is a legitimate memory-corruption RCE in the world's most-deployed browser and should be patched promptly via Chrome's auto-update, but as a standalone (sandbox-confined, interaction-dependent, no KEV/POC) issue it is not a drop-everything emergency relative to an unauthenticated server RCE. Treat the 8.8 as an upper bound pending the sandbox-containment caveat. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing malformed content that triggers the compositing memory-corruption bug, then lures a victim to visit it (link, ad, or malvertising). When the victim's vulnerable Chrome (prior to 156.0.8078.47) renders the page, the attacker gains arbitrary code execution within the renderer sandbox; full system compromise would require a further sandbox-escape exploit. No public proof-of-concept is referenced at time of analysis. |
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's Compositing component allows unauthenticated remote attackers to execute arbitrary code inside the renderer sandbox by convincing a victim to open a crafted HTML page in desktop versions prior to 156.0.8078.47. User interaction is mandatory, and successful exploitation is confined to the sandbox, so host compromise would require chaining a separate sandbox-escape vulnerability. No public exploit was identified at the time of analysis, and Google has released a patched version; the 8.8 CVSS score contrasts with Chromium's Medium severity rating because of the sandbox confinement.
RemediationAI
Update Google Chrome desktop to version 156.0.8078.47 or later; Google has released the fix and details are in the Stable Channel advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html. Verify the installed version via chrome://version and restart the browser after updating, since Chrome typically applies updates on restart. For managed environments, use enterprise update policies to force the fixed build and confirm compliance; until the update is deployed, restrict browsing to trusted sites and consider isolating Chrome in a sandboxed or virtualized environment to reduce exposure, recognizing that these are compensating controls rather than a fix.
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
CVE-2026-113069 is a CWE-119 memory-corruption flaw in the Compositing component of Chromium, the layer that merges rendered content into the final frame displayed by the browser. Processing a crafted HTML page can trigger improper bounds handling, leading to memory corruption that an attacker can potentially leverage for arbitrary code execution within the renderer process. The affected code is in Google Chrome desktop builds earlier than 156.0.8078.47; no special configuration is needed beyond standard browsing. Because the renderer is sandboxed, the flaw alone does not yield host-level compromise-the CVSS 8.8 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects high confidentiality, integrity, and availability impact within that sandbox, while Chromium's Medium rating and the independent assessment emphasize that a separate sandbox escape is required for broader system 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 needs only a victim visit (AV:N/AC:L/PR:N/UI:R); code exec yields high C/I/A but stays within the renderer sandbox, so scope unchanged (S:U).
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Memory corruption in Compositing in Google Chrome 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: Medium)
Executive ViewAI
Google Chrome desktop versions prior to 156.0.8078.47 contain a high-severity memory-corruption flaw in the Compositing component that could allow code execution inside the browser’s renderer sandbox when a user opens a crafted HTML page. Because exploitation requires user interaction and is confined to the sandbox-full host compromise would need a separate sandbox-escape chain-the immediate organizational risk is concentrated in unpatched, internet-connected desktop browsers rather than automatic host takeover. No public exploit was identified at the time of analysis, but the broad Chrome deployment base and the availability of a vendor fix make prompt remediation a leadership priority.
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