Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to attacker-controlled page
-
DeliveryServe crafted HTML and JavaScript
-
ExploitTrigger DataTransfer use-after-free
-
ExecutionReclaim freed memory, corrupt state
-
ImpactExecute arbitrary code in 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 | Exploitation requires the victim to actively load a crafted HTML page in a vulnerable Google Chrome build prior to 156.0.8078.47 (UI:R / UI:P), so it is not a drive-by against a service - it depends on social engineering or a compromised/malicious site. The use-after-free is in the DataTransfer interface, which backs clipboard and drag-and-drop operations, so the trigger involves JavaScript exercising those data-transfer paths. The decisive limiting factor is that resulting code execution is confined to the renderer sandbox (S:U, 'inside the sandbox' per vendor text); meaningful host impact requires chaining a separate sandbox-escape vulnerability, which is not provided here. |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U) describes a network-reachable, low-complexity, unauthenticated flaw that requires user interaction, scoring 8.8 - consistent with a browser renderer bug triggered by visiting a page. However, a critical nuance tempers this: the description explicitly states code execution occurs 'inside the sandbox,' meaning this alone does NOT yield host compromise and would need to be chained with a separate sandbox-escape to achieve full RCE on the system. This also aligns with Chromium's own 'Medium' internal severity rating, which conflicts with the elevated 8.8 CVSS score - the discrepancy is best explained by the sandbox confinement limiting real-world impact. No EPSS score was provided in the input, so exploitation probability cannot be quantified. The vulnerability is NOT in CISA KEV and no public exploit code is referenced, so there is no public exploit identified at time of analysis. Net assessment: patch promptly because Chrome is ubiquitous and UAF bugs are historically exploitable, but this is a sandboxed renderer bug (not an immediate full-system takeover) and currently shows no evidence of active exploitation, placing it as important-but-not-emergency relative to confirmed in-the-wild Chrome zero-days. |
| Exploit ScenarioDerived | An attacker hosts or injects a crafted HTML page containing JavaScript that manipulates the DataTransfer object (e.g., via drag-and-drop or clipboard operations) to trigger a use-after-free. When a victim running a vulnerable Chrome build (prior to 156.0.8078.47) visits the page, the freed memory is reclaimed and reused to corrupt renderer state, allowing arbitrary code execution within the renderer sandbox. No public proof-of-concept is referenced, and full system 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
Use-after-free memory corruption in Google Chrome's DataTransfer interface affects builds prior to 156.0.8078.47 and lets a remote attacker execute arbitrary code within the renderer sandbox by convincing a victim to load a crafted HTML page. No public exploit code or confirmed active exploitation is identified in the available intelligence, though the vendor rates the issue Medium severity while the CVSS 3.1 vector scores 8.8 (AV:N/AC:L/PR:N/UI:R/S:U). Because the sandbox confines execution, full host compromise would require chaining an additional sandbox-escape vulnerability, so practical risk centers on renderer-level compromise, data theft from the browsing session, and denial of service.
RemediationAI
Update Google Chrome to 156.0.8078.47 or later (Vendor-released patch: 156.0.8078.47), as documented in the stable channel advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html; enterprise fleets should push the update via their management console and verify the reported browser version. Where immediate upgrade is impossible, reduce exposure by restricting navigation to trusted sites through policy allowlists, enforcing site isolation, and disabling or limiting drag-and-drop/clipboard-heavy web applications - accepting the trade-off of reduced usability for internal web tooling. Because the impact is confined to the renderer sandbox until a separate escape is chained, keeping the browser sandbox enabled and hardening the OS against sandbox escapes materially lowers residual risk; disabling the sandbox as a workaround is strongly discouraged.
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
CWE-416 use-after-free: the DataTransfer interface - the browser API underlying clipboard, drag-and-drop, and paste operations in Chromium - can be made to reference a freed object when JavaScript exercises those data-transfer paths, producing exploitable memory corruption. This class of bug arises when an object's lifetime is not correctly tracked across asynchronous or event-driven code paths, allowing an attacker to reclaim the freed allocation with controlled data and hijack control flow in the renderer. CPE and EUVD data place the affected component in Google Chrome builds earlier than 156.0.8078.47; the flaw is renderer-process reachable, and per vendor text code execution occurs inside the sandbox rather than at browser or OS privilege level. Tags associate it with RCE, memory corruption, and denial of service.
Know when the next one hits your stack
- 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 no privileges (PR:N) but requires the victim to visit (UI:R); sandboxed renderer code execution keeps scope unchanged (S:U) with high C/I/A within that process.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Use after free in DataTransfer 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 builds prior to 156.0.8078.47 contain a high-severity memory-corruption flaw in the DataTransfer interface that could allow a malicious webpage to compromise the browser renderer, exposing browsing-session data or disrupting endpoints. Although no public exploit was identified at time of analysis, the broad Chrome footprint means unpatched users remain exposed until the vendor update is deployed. Leadership should prioritize browser patching because the issue is unauthenticated and requires only user interaction.
Apply vendor patch.
Threat Intelligence Overview
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.
EUVD-2026-105577
GHSA-6qp6-hpgv-7qxf
NVD
CVE.org
EPSS
Exploit-DB