EUVD-2026-105651
GHSA-4g8h-7fpj-wfh9
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitPage triggers memory corruption in SiteIsolation
-
ExecutionCorrupt memory bends control flow
-
ImpactExecute arbitrary code within renderer sandbox
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 a user to actively load attacker-controlled web content (a crafted HTML page) in Chrome prior to 156.0.8078.47 - the CVSS UI:R and the description both confirm victim interaction is mandatory, which rules out silent/wormable mass exploitation. No authentication is required (PR:N). The primary limiting factor beyond user interaction is that code execution is confined 'inside the sandbox' per the vendor description, so a full host compromise would additionally require a separate sandbox-escape vulnerability not covered by this CVE. No special non-default configuration is needed; default Chrome with Site Isolation (standard since Chrome 67) is affected. |
| Impact | Signals are mixed and should be read together. The NVD 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 remote, low-complexity, unauthenticated bug needing only user interaction (visiting a page) - classic drive-by browser-exploit shape. However, the vendor's own Chromium severity rating is Medium, and the description explicitly scopes code execution to 'inside the sandbox,' meaning a successful exploit yields attacker code in a renderer/isolated process rather than full host compromise - a material gap between the 8.8 numeric score and the realistic blast radius. No EPSS score was supplied, the CVE is NOT on CISA KEV, and no POC is referenced, so there is no evidence of active or imminent exploitation. SSVC-style read: exploitation = none observed, automatable = no (requires victim to load a crafted page), technical impact = partial (sandbox-confined). Net: a legitimately patch-worthy remote browser flaw, but currently a routine-priority Chrome update rather than an emergency - the high CVSS overstates urgency relative to the Medium vendor rating, sandbox confinement, and absence of KEV/POC/EPSS data. Note: a renderer-sandbox RCE is typically only fully dangerous when chained with a separate sandbox-escape bug, which this CVE does not provide. |
| Exploit ScenarioDerived | An attacker hosts or injects a crafted HTML page (e.g., via a malicious site, compromised ad, or iframe) and lures a user to open it in a vulnerable Chrome build. The page triggers memory corruption in the SiteIsolation component, potentially allowing arbitrary code execution confined to the browser sandbox; no public exploit code has been identified at time of analysis, and the attack requires user interaction (loading the page). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Memory corruption in Chrome's SiteIsolation component lets a remote attacker who convinces a user to open a crafted HTML page potentially execute arbitrary code inside the browser sandbox on Chrome builds prior to 156.0.8078.47. Exploitation is not silent or wormable: the CVSS vector AV:N/AC:L/PR:N/UI:R means no credentials are needed but victim interaction is mandatory, and the vendor scopes the outcome to code execution 'inside the sandbox,' so full host compromise would require chaining a separate sandbox-escape flaw. Google rates the underlying bug Medium severity while the derived CVSS base score is 8.8; no public exploit code or active exploitation is identified in the available intelligence at time of analysis, and a vendor patch (156.0.8078.47) is already published.
RemediationAI
Vendor-released patch: upgrade Google Chrome to 156.0.8078.47 or later from the stable channel advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html, then verify the installed version via chrome://version and restart all browser processes so the new binary is active. Enterprise fleets should force the update through the Chrome Browser Cloud Management / Google Update policies (UpdateDefault, automatic updates enabled) and confirm compliance, since the flaw is reachable from ordinary browsing with no special configuration. Do not attempt to mitigate by disabling Site Isolation (for example the --disable-site-isolation-trials switch) or by turning off the renderer sandbox: the vendor's description confines the impact to code execution inside the sandbox precisely because those mitigations are in place, and removing either widens exposure to this and other memory-corruption bugs rather than narrowing it. Where patching must be staged, reduce the attack window by restricting untrusted web content through proxy/URL filtering and by keeping users on browsers not affected by this Chromium revision; both are partial measures with real usability cost and do not substitute for the 156.0.8078.47 update, and there is no vendor-issued configuration workaround for this CVE.
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 CWE-119 (improper restriction of operations within the bounds of a memory buffer), i.e. classic memory corruption in native Chromium code. The affected subsystem is SiteIsolation - Chrome's process-per-site architecture (introduced broadly in Chrome 67) that places cross-site documents in separate renderer processes and enforces origin-based boundaries via out-of-process iframes and the browser-side site-instance checks. A memory-safety defect in that boundary logic can be triggered by attacker-controlled markup, corrupting renderer-side memory and giving the attacker a controlled execution primitive confined to the sandboxed renderer process. Because the affected code path sits in the isolation machinery itself, the bug is reachable from ordinary web content with default configuration; there is no non-default setting prerequisite beyond running a Chrome build earlier than 156.0.8078.47. CPE enumeration was not supplied in the feed data; EUVD lists the affected range as Chrome versions below 156.0.8078.47.
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 with no auth (AV:N/PR:N) but mandatory user interaction (UI:R); sandbox-confined code execution keeps scope unchanged (S:U) with high renderer-process C/I/A impact.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Memory corruption in SiteIsolation in Google Chrome 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: Medium)
Executive ViewAI
Google Chrome builds prior to 156.0.8078.47 contain a high-severity memory-corruption flaw in SiteIsolation that could allow a crafted webpage to execute code inside the browser sandbox, affecting any workforce that relies on Chrome for web access. The issue requires user interaction and no credentials, and no public exploit identified at time of analysis; however, the broad Chrome footprint means unpatched endpoints and high-exposure users warrant prioritized remediation.
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