EUVD-2026-105691
GHSA-82p7-pc34-2c85
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 Loader
-
ExecutionReclaim freed object with controlled data
-
ImpactExecute arbitrary code within 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 | Requires the victim to actively load attacker-controlled content in Chrome prior to 156.0.8078.47 (UI:R - user interaction via visiting a crafted HTML page); no authentication or special configuration is needed since the vulnerable Loader code path is reachable in default browsing. The principal limiting factor is Chrome's renderer sandbox: resulting code execution is confined to the sandboxed process, so a separate sandbox-escape would be needed for full host compromise, and the victim must be enticed to open the malicious page. |
| Impact | Signals conflict and must be weighed carefully. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R, C:H/I:H/A:H → 8.8 High) frames this as a network-reachable, unauthenticated memory-corruption bug requiring only that a victim load a crafted page. However, Google's own Chromium security severity rating is explicitly 'Low', and the description qualifies impact as code execution 'inside the sandbox' - i.e. confined to the renderer process rather than the host OS. This is the central tension: the generic 8.8 score does not account for Chrome's sandbox, which is why Chromium rates it Low. No EPSS score was provided, so exploitation probability cannot be quantified. There is no CISA KEV listing and no public exploit referenced, so there is no public exploit identified at time of analysis. Net assessment: this is a patch-on-normal-cadence browser bug, not an emergency - the sandbox containment and Low vendor severity substantially temper the headline 8.8. Use-after-free bugs in Chrome's Loader are historically chainable with a sandbox-escape to achieve full RCE, so it should still be patched promptly, but on current evidence it is a 'high-CVSS, moderate-real-risk' issue rather than an actively exploited priority. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing markup/resource-loading sequences crafted to trigger the use-after-free in Chrome's Loader component. A victim is lured to visit the page (UI:R), and the freed-then-reused object is manipulated to achieve arbitrary code execution within the renderer sandbox. 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 Loader component before 156.0.8078.47 allows an unauthenticated remote attacker who persuades a victim to load a crafted HTML page to execute arbitrary code inside the renderer sandbox. Exploitation requires user interaction (UI:R) and no special configuration, but the impact is bounded by Chrome's sandbox; full host compromise would require a separate sandbox escape. No public exploit code or CISA KEV entry was identified in the supplied intelligence, and Google rates the issue Chromium severity Low despite the 8.8 CVSS score.
RemediationAI
Upgrade Google Chrome to 156.0.8078.47 or later; this is the vendor-released patch version documented in the Chrome stable-channel advisory (https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html). Confirm the installed version via chrome://settings/help and allow auto-update to complete, then restart the browser. No direct configuration workaround fixes the use-after-free; compensating controls are to keep Chrome's sandbox enabled and the host OS fully patched so a separate sandbox escape is harder, to restrict browsing to trusted content or isolate Chrome in a virtualized/remote-browsing environment for high-risk users, and to prioritize updates on systems where users routinely open untrusted HTML. These controls reduce exposure but do not remove the underlying flaw.
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, a use-after-free in Chrome's Loader component: an object is freed while a reference remains, and a crafted HTML page can cause the stale reference to be reused, leading to memory corruption and potentially controllable code execution within the renderer process. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) describes a network-reachable, low-complexity, unauthenticated attack that still needs the victim to open the malicious page. The 8.8 score reflects high confidentiality, integrity, and availability impact in the exploited component, while Google's Chromium severity rating of Low and the 'inside the sandbox' wording indicate the code execution is confined to Chrome's sandboxed renderer; escaping to the host requires an additional vulnerability. No CPE strings were supplied; the affected component is the Chrome desktop browser before 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 reached without privileges (AV:N/PR:N) but requires the victim to open it (UI:R); sandboxed RCE keeps scope unchanged (S:U) while compromising renderer confidentiality, integrity and availability.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Use after free in Loader 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: Low)
Executive ViewAI
Google Chrome releases prior to 156.0.8078.47 contain a memory-safety flaw in the Loader component that a malicious web page could use to execute code inside the browser's renderer sandbox. The practical blast radius is constrained by Chrome's sandbox architecture and Google's own Low Chromium severity rating, and no public exploit or active exploitation has been identified. Exposure is still broad because Chrome is widely deployed across the workforce, so leadership should treat this as a time-bound patch-management priority 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
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