Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitDeliver malicious media content
-
ExecutionTrigger use-after-free in Media component
-
ImpactExecute arbitrary code inside 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 attacker-controlled web content in Chrome - the CVSS UI:R and the description's 'crafted HTML page' confirm user interaction (navigating to or being redirected to a malicious/compromised page) is mandatory; it is not a zero-click flaw. The vulnerability lies in Chrome's Media component, so the malicious page must deliver media content that drives the vulnerable code path. The primary limiting factor is that code execution is confined to the renderer sandbox (S:U, 'inside the sandbox'): absent a separately chained sandbox-escape vulnerability, the attacker does not directly gain host-level code execution. No authentication is required (PR:N), and default Chrome configurations are affected (no non-default setting is named). |
| Impact | Signals are largely consistent and point to a genuinely serious but not yet emergency-level issue. 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 network-reachable, unauthenticated, low-complexity code execution that requires only that a victim load a crafted HTML page - the classic drive-by browser exploitation profile. The scope-unchanged (S:U) metric aligns precisely with the description's key qualifier that code executes 'inside the sandbox,' meaning this is a renderer-level RCE without a confirmed sandbox escape, so blast radius is limited unless chained with a separate sandbox-escape bug. Counterbalancing the high CVSS, EPSS is very low at 0.21% (11th percentile), the CVE is NOT on CISA KEV, and no public exploit was identified in the provided data, so there is no evidence of current real-world exploitation. The low EPSS is typical for a freshly-disclosed Chrome use-after-free that has not yet been weaponized publicly; it does not contradict the high severity. Net: this is a real patching priority because Chrome's ubiquity and UAF bugs' historical exploitability make it an attractive target, but at time of analysis it is a 'patch promptly, not drop-everything' item rather than an actively-exploited emergency. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing malicious media content that triggers the use-after-free in Chrome's Media component when rendered. A victim running a vulnerable Chrome version (prior to 155.0.8059.79) simply visits the page, and the attacker gains arbitrary code execution within the constrained renderer sandbox. No public exploit code was identified at time of analysis, and low attack complexity (AC:L) means no special timing or environmental conditions are required beyond getting the victim to load the content. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Use-after-free in Google Chrome's Media component before version 155.0.8059.79 allows a remote attacker to achieve arbitrary code execution inside the renderer sandbox by convincing a user to open a crafted HTML page that drives the vulnerable media-parsing code path. Exploitation requires user interaction (the victim must navigate to or be redirected to attacker-controlled content), and the resulting code execution is confined to the sandbox, meaning host compromise would require chaining a separate sandbox-escape flaw. No public exploit code has been identified at time of analysis, EPSS is low (0.21%, 11th percentile), and Google has released a fixed build, so risk is serious but not emergency-level; priority should follow normal rapid-patching timelines.
RemediationAI
Vendor-released patch: upgrade Google Chrome to 155.0.8059.79 or later, distributed through the Chrome stable channel per the advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_01668083673.html; organizations that track the extended stable train should apply the corresponding build referenced at https://chromereleases.googleblog.com/2026/10/extended-stable-update-for-desktop_0571684596.html. Because exploitation requires the user to load attacker-controlled media content, the highest-value compensating control while patching is enforced auto-update plus a restart of the browser (Chrome does not apply the fix to a running session), and network-level blocking of untrusted media delivery is only a partial mitigation with the obvious trade-off of breaking legitimate video content. Disabling or restricting media playback via enterprise policy or site-isolation/extension controls reduces exposure but degrades normal browsing functionality and is not a substitute for the update; Chromium-based third-party browsers should be upgraded to a build that has rebased onto 155.0.8059.79 once their vendors publish it. Given the absence of a confirmed public exploit and the low EPSS score, remediation can follow a standard patch cycle rather than an emergency one, but the update should not be deferred indefinitely.
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 a use-after-free (CWE-416) in Chromium's Media subsystem, the set of components responsible for demuxing, decoding and rendering audio/video content (media pipelines, codec glue, and the media element resource lifecycle). In a UAF, an object is freed while a dangling reference remains; a crafted HTML page feeding malformed or specially timed media content can cause the freed memory to be reused, giving the attacker control over the contents of that allocation and, typically, redirecting a virtual call or function pointer to attacker-chosen code. Because this is a memory-corruption class primitive (also consistent with the RCE and Denial of Service tags attached to the record), the practical outcome is code execution within the Chrome renderer process that hosts the Media code, not in the browser process or on the host. The CPE/version data place the affected surface at Google Chrome builds before 155.0.8059.79, with the fix landing in that release (Chromium issue 568037533 tracks the underlying bug).
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 with no auth (AV:N/PR:N) but requires the victim to load it (UI:R); sandbox-contained RCE keeps S:U while renderer compromise yields full C/I/A:H.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Use after free in Media in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
A use-after-free in Google Chrome's Media component before 155.0.8059.79 could allow a remote attacker to execute arbitrary code inside the browser's renderer sandbox if a user opens crafted HTML content, though full host compromise would require chaining a separate sandbox-escape flaw. Google has released a fixed build and no public exploit identified at time of analysis, with low EPSS, so the organizational risk is serious but not emergency-level. Leadership should ensure rapid, normal-cycle patching across all Chrome users, especially those handling sensitive data or privileged web applications.
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-100649
GHSA-pqq3-537g-4v8h
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB