EUVD-2026-111454
GHSA-jgvf-x6pf-xr69
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 ImageCapture
-
ExecutionReclaim and corrupt freed heap object
-
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 | Exploitation requires user interaction (CVSS UI:R): the victim must load an attacker-controlled crafted HTML page in an unpatched Chrome build prior to 156.0.8078.73. No authentication is required (PR:N) and no special non-default configuration is indicated. The principal limiting factor is that arbitrary code execution is confined to the renderer sandbox per the description, so by itself this flaw does not yield host-level compromise without an additional sandbox-escape vulnerability; the requirement that a user actively visit the page is the other key constraint on real-world exploitation. |
| Impact | This is a genuine priority within the browser-exploitation context, but its real-world impact is bounded by the sandbox. 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 flaw requiring only that a victim visit a crafted page - the classic drive-by browser profile. However, the description is explicit that code execution occurs 'inside the sandbox,' meaning the scope is Unchanged (S:U) and full host compromise would require a separate sandbox-escape chain not covered by this CVE; the 8.8 score reflects renderer-process compromise, not system takeover. No EPSS score was supplied, this CVE is NOT in CISA KEV, and no public exploit was provided - the two references to the Chromium issue tracker are typically access-restricted and are not working exploit code. The vendor's own severity is 'High,' and the vuln.today decision label is 'this_week' (not act_now/emergency), which is consistent with a serious-but-not-actively-exploited memory-corruption bug. Net: treat as a routine-but-prompt Chrome update priority rather than an emergency, absent any exploitation signal. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing crafted content that drives the ImageCapture component into a use-after-free state; a victim running an unpatched Chrome (prior to 156.0.8078.73) is lured to the page via phishing, malvertising, or a watering-hole. Triggering the freed-object reuse lets the attacker execute arbitrary code within the renderer sandbox, giving a foothold that would then need a separate sandbox escape to reach the host. No public exploit was identified at time of analysis; the referenced Chromium bug entry is not verified working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
A use-after-free in Chrome's ImageCapture component lets remote attackers who convince a victim to open a crafted HTML page execute arbitrary code - but, per the advisory, that execution is confined to the renderer sandbox rather than the host. Chrome builds prior to 156.0.8078.73 are affected and the vendor has released a fix; exploitation requires user interaction (CVSS UI:R) with no authentication or special configuration needed. No public exploit or active exploitation is identified in the supplied data, and the assessed priority places remediation in the near-term 'this week' window rather than emergency status, because host compromise would additionally require a separate sandbox-escape flaw.
RemediationAI
Upgrade Google Chrome to 156.0.8078.73 or later via the stable channel release described at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_0562499947.html; a vendor patch is available, and the fix is the complete remediation because the root cause is a memory lifetime error in ImageCapture that cannot be safely neutralised by configuration. Confirm the installed version in chrome://settings/help or chrome://version, then restart the browser so the update is applied. Chromium-based browsers other than Chrome should be updated to builds that incorporate the corresponding Chromium fix, checked against their own vendor advisories. Because exploitation requires the victim to load crafted HTML (UI:R) and code execution is confined to the renderer sandbox, the practical interim exposure reduction is to restrict browsing to trusted sites and keep the browser current until the update is deployed fleet-wide; there is no documented flag or policy in the supplied data that disables the affected ImageCapture path, and any such feature-level change would break legitimate camera/image-capture functionality if applied.
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 a CWE-416 use-after-free, a memory-safety class in which an object is freed while a dangling reference to it remains and is later dereferenced, allowing an attacker to influence what occupies the freed memory. Here the affected object lives in the ImageCapture component of Chromium's Blink web platform stack, which handles image capture from camera-backed media streams exposed to web content. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates the attack is network-delivered with low complexity and no privileges, but requires the victim to load attacker-controlled content; it also scores scope as unchanged, consistent with the description's statement that code execution occurs inside the sandbox. The exact object lifetime error and the specific JavaScript/HTML primitives that trigger it are not described in the available sources; the Chromium issue tracker entry (issues.chromium.org/issues/574027204) is the appropriate place to confirm the reproducer details, and such tracker entries are typically restricted until a fix ships. Affected builds are those earlier than 156.0.8078.73 as recorded in the EUVD affected-version data.
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 drives the flaw (AV:N/AC:L/PR:N) but needs the victim to visit it (UI:R); impact stays in the sandboxed renderer so S:U with full C/I/A loss there.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Use after free in ImageCapture in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Articles & Coverage 1
Executive ViewAI
Google Chrome versions prior to 156.0.8078.73 contain a high-severity use-after-free vulnerability in the ImageCapture component (CVE-2026-118334) that could allow code execution within the browser's renderer sandbox if a user visits a malicious webpage. While the sandbox limits the immediate blast radius to the browser process, the incident affects all employees using unpatched Chrome and could lead to data exposure or further compromise if chained with a sandbox escape. Leadership should prioritize rapid patching to maintain endpoint integrity and reduce risk of a broader breach.
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