EUVD-2026-105624
GHSA-xw49-fp4r-vg2c
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitTrigger use-after-free in SiteIsolation
-
ExecutionCorrupt renderer process memory
-
ImpactExecute arbitrary code within 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 the victim to load attacker-controlled content - a crafted HTML page - in an unpatched Google Chrome build prior to 156.0.8078.47 (UI:R, confirmed by vector and description); no authentication or special non-default configuration is needed, as SiteIsolation is a standard Chrome feature. The principal limiting factor is that successful code execution is confined to the renderer sandbox (CVSS S:U): meaningful host compromise requires chaining a separate sandbox-escape vulnerability. User interaction (visiting/rendering the malicious page) is the key exploitation barrier, mitigable by prompt patching. |
| Impact | This is a genuinely high-priority patch target despite the absence of confirmed exploitation. The 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, low-complexity, unauthenticated memory-corruption flaw requiring only that a victim load a crafted HTML page - a trivially satisfied condition for a web browser. CWE-416 (use-after-free) in SiteIsolation is a classic, reliably exploitable renderer bug class that Chromium rates High. However, several real-risk-moderating signals must be weighed: the description explicitly states code execution occurs 'inside the sandbox,' so S:U (scope unchanged) is correct and a separate sandbox-escape chain is required for full host compromise - raw CVSS 8.8 overstates standalone impact. No EPSS score, CISA KEV listing, or public POC is present in the provided intelligence, so there is no evidence of active exploitation or weaponization: this is a prophylactic high-severity fix, not an emergency KEV-grade incident. The dominant risk driver is prevalence (Chrome's enormous install base) combined with proven exploitability of the bug class, not any demonstrated in-the-wild activity. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing specially crafted HTML/JavaScript that triggers the use-after-free in Chrome's SiteIsolation component when a victim browses to it. Successful exploitation lets the attacker execute arbitrary code within the renderer sandbox; to escape the sandbox and compromise the host, the attacker would need to chain this with an additional vulnerability. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Use-after-free in Google Chrome's SiteIsolation component before 156.0.8078.47 allows unauthenticated remote attackers to trigger memory corruption and execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page. The attack requires user interaction (UI:R) and does not by itself escape Chrome's sandbox, so host compromise would require chaining an additional sandbox-escape vulnerability. No public exploit identified at time of analysis, but the vendor has released a fixed build and the issue is rated High severity.
RemediationAI
Vendor-released patch: Google Chrome 156.0.8078.47. Update Chrome to 156.0.8078.47 or later through the browser's auto-update mechanism, verify the version via chrome://settings/help, and fully restart the browser so the new binary is loaded; enterprise administrators should enforce the minimum version through their Chrome update policies. See the vendor advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html and the Chromium issue at https://issues.chromium.org/issues/560749221. If immediate patching is not possible, route untrusted web browsing through remote browser isolation or restrict access to untrusted HTML content, accepting the added latency and usability trade-off; do not disable Site Isolation as a workaround, because that weakens the browser's process boundary and can increase the impact of a renderer compromise.
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 root cause is CWE-416 (use-after-free), in which Chrome's SiteIsolation component continues to reference memory after it has been freed, enabling memory corruption that can be steered toward code execution in the renderer process. Site Isolation is a standard Chrome security architecture feature that places content from different sites into separate renderer processes, and the Chrome sandbox constrains what a compromised renderer can do; the CVSS vector's S:U scope reflects that the demonstrated impact is within the vulnerable component rather than a direct host compromise. The CVSS vector AV:N/AC:L/PR:N/UI:R indicates a network-reachable, low-complexity issue requiring no privileges but requiring the victim to render attacker-controlled HTML. The fixed version boundary is Chrome 156.0.8078.47; no CPE strings were supplied, but the EUVD affected-version data identifies the pre-fix Chrome build boundary.
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 victim interaction (AV:N/UI:R) with no auth (PR:N); code runs in the renderer sandbox so scope is unchanged (S:U) with full renderer-process C/I/A impact.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Use after free in SiteIsolation 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: High)
Executive ViewAI
Google Chrome builds prior to 156.0.8078.47 contain a high-severity memory-corruption vulnerability in the SiteIsolation component that creates a workforce-wide browser risk for employees who load crafted web content. Although the flaw does not by itself break Chrome's renderer sandbox and no public exploit identified at time of analysis, host compromise would require chaining an additional sandbox-escape issue, so leadership should treat it as an elevated but manageable endpoint exposure. Because a vendor patch is available, the priority is rapid update compliance across the Chrome estate to reduce exposure for all browser users.
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
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.
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