EUVD-2026-111450
GHSA-6qq7-6j33-xfwv
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to attacker-controlled web page
-
ExploitServe crafted media within HTML
-
ExecutionTrigger memory corruption in Media component
-
ImpactExecute arbitrary code inside 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 Chrome user (versions prior to 156.0.8078.73) to load a crafted HTML page containing malicious media content that is processed by the Media component (UI:R) - there is no authentication requirement (PR:N). The key limiting factors are: (1) mandatory user interaction, since the victim must navigate to or render the attacker's page; and (2) scope containment - arbitrary code execution is confined to the renderer sandbox (S:U, 'inside the sandbox' per the description), so a defender's practical worst case for this single flaw is renderer-process compromise rather than full host takeover absent a chained sandbox escape. The specific media format or configuration that triggers the memory corruption is not described in the available sources. |
| Impact | This is a genuine high-priority patch item but not a drop-everything emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) reflects a network-reachable, low-complexity, unauthenticated flaw that requires user interaction (visiting a crafted page), with high impact to confidentiality, integrity and availability. Critically, the description constrains the outcome to 'execute arbitrary code inside the sandbox' and the scope is Unchanged (S:U), so code execution is confined to the renderer process - full host compromise would require chaining a separate sandbox-escape vulnerability, which materially lowers standalone real-world impact. The vuln.today decision label is 'this_week', consistent with a serious browser memory-corruption bug that is not under active exploitation. No EPSS score, no CISA KEV listing, and no confirmed public exploit code were provided in the input; the referenced chromium issue tracker entry (issues.chromium.org/572878518) is a bug record, typically access-restricted, not verified working exploit code. No signals conflict: all available evidence points to a high-severity but currently unexploited renderer-sandboxed RCE. The main uncertainty is the trigger mechanism - the sources do not describe how the Media memory corruption is reached beyond 'a crafted HTML page.' |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing crafted media content and lures a Chrome user to visit it (e.g., via a link or malvertising). When Chrome's Media component parses the content, memory corruption is triggered, potentially allowing arbitrary code execution within the renderer sandbox. No public exploit was identified in the provided data; achieving impact beyond the sandbox would require a separate escape. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Memory corruption in Google Chrome's Media component can let a remote, unauthenticated attacker execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page, affecting Chrome releases prior to 156.0.8078.73. Exploitation requires user interaction and, with scope unchanged, is limited to renderer-process compromise rather than full host takeover unless combined with a separate sandbox escape. No public exploit identified at time of analysis; the vendor has released a fixed build, and this is a high-priority patch item rather than a drop-everything emergency.
RemediationAI
Update Google Chrome to 156.0.8078.73 or later; the vendor reports a patch is available, and the stable-channel advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_0562499947.html provides the release details. No workaround is described in the supplied data. The description limits impact to code execution inside the renderer sandbox, so a successful single-CVE attack is contained to the renderer process unless the attacker chains a separate sandbox escape; that containment does not remove the need to apply the 156.0.8078.73 update. Chromium issue 572878518 is available for technical tracking.
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
Google Chrome's Media component parses and decodes media content; CVE-2026-118327 is classified under CWE-119 (improper restriction of operations within the bounds of a memory buffer), the memory-corruption class implicated by the supplied 'Buffer Overflow' and 'RCE' tags. The provided CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) describes a network-reachable, low-complexity attack that needs no privileges but requires user interaction, with high confidentiality, integrity, and availability impact and unchanged scope; the description states code execution is contained 'inside the sandbox.' The Chrome stable-channel advisory and Chromium issue 572878518 are the primary references, but they do not identify the specific media format, parser, or configuration that triggers the corruption, so the exact trigger is not described in the available sources. EUVD-2026-111450 records the affected boundary as Chrome versions below 156.0.8078.73; no CPE strings were supplied.
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 delivery (AV:N, AC:L, PR:N) requires the victim to load the page (UI:R); code execution stays within the renderer sandbox so scope is Unchanged with full C/I/A impact.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Memory corruption in Media in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Articles & Coverage 1
Executive ViewAI
Google Chrome's Media component contains a high-severity memory corruption vulnerability that allows remote attackers to execute arbitrary code within the browser's renderer sandbox when a user visits a malicious page. This affects all Chrome versions prior to 156.0.8078.73 and requires user interaction, meaning employees could be exposed simply by browsing the web. While no public exploit has been identified and the impact is limited to the renderer process unless combined with a separate sandbox escape, the widespread use of Chrome across the organization and the potential for follow-on attacks make prompt patching critical.
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