EUVD-2026-89385
GHSA-fcf3-fgrp-9hp7
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious page
-
DeliveryServe crafted HTML to Chrome
-
ExploitTrigger use-after-free in Views
-
ExecutionCorrupt memory and escape sandbox
-
ImpactExecute arbitrary code on host
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 open or navigate to an attacker-controlled HTML page in an unpatched Chrome build before 154.0.8037.92 (UI:R / social engineering). No authentication or special browser configuration is needed - it affects default Chrome installations - but exploitation is limited by the need for user interaction and by the difficulty of achieving a reliable use-after-free-to-code-execution sandbox escape. Applies to desktop Chrome per the advisory. |
| Impact | This is a genuine high-priority issue. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, base 9.6) reflects a network-reachable, low-complexity, unauthenticated flaw whose only gating factor is user interaction (visiting a malicious page), and the S:C scope change is corroborated by the description's explicit 'execute arbitrary code outside the sandbox' - a sandbox escape, which is the most severe class of browser bug. The CWE-416 use-after-free classification and 'Memory Corruption'/'RCE' tags are consistent. Countervailing signals: no EPSS score is provided, there is no CISA KEV listing, and no public exploit code is identified, so despite the 9.6 the observable exploitation evidence is currently absent. Google rates the Chromium severity 'High' rather than 'Critical', consistent with the requirement for social engineering / user interaction. Net: treat as high priority for patching given ubiquity + sandbox-escape RCE, while noting exploitation is not yet confirmed in the wild. |
| Exploit ScenarioDerived | An attacker crafts a malicious HTML page that triggers the use-after-free in Chrome's Views UI component and lures a victim to open it (malvertising, phishing link, or compromised site). Successful exploitation corrupts memory and executes attacker-controlled code outside the browser sandbox on the victim's host. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 29, 2026
A use-after-free in Chrome's Views UI framework allows an unauthenticated remote attacker who convinces a victim to open a crafted HTML page to execute arbitrary code outside the browser sandbox in Google Chrome desktop builds prior to 154.0.8037.92. Per the CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), no credentials or special browser configuration are required - default installations are affected - but exploitation depends on user interaction with attacker-controlled content and on overcoming the difficulty of turning a use-after-free into a reliable sandbox escape, so a working exploit is not trivial. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited; a vendor patch (154.0.8037.92) is available, which makes rapid update the decisive control.
RemediationAI
Upgrade Google Chrome to version 154.0.8037.92 or later - this is the vendor-released fix. Use the built-in updater (chrome://settings/help) or the stable-channel advisory at https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_01807488085.html to verify the build, and force the update fleet-wide with enterprise policy or your software-management tooling, since a restart of the browser is required for the new binary to take effect. Because the bug resides in the browser's own UI framework rather than in page-renderable content, renderer-level hardening such as Site Isolation does not mitigate it, and there is no meaningful configuration toggle to disable the vulnerable Views code path - the practical trade-off is that updating and restarting Chrome may interrupt active sessions, which is still the correct action given sandbox-escape impact. Until patched builds are deployed, reduce exposure by limiting browsing of untrusted or unsolicited links (the attack requires the victim to open an attacker-controlled HTML page, i.e., a social-engineering step) and by running Chrome under a restricted OS account or virtualized environment so a successful escape does not inherit broad user privileges; both measures degrade usability for legitimate web work and are compensating controls only, not substitutes for the update.
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 Views, Chromium's cross-platform native UI toolkit that renders the desktop browser's own widgets such as menus, dialogs, toolbars, and other browser-chrome elements. In a use-after-free, an object is released while a dangling reference to it remains reachable; the freed memory can subsequently be reused for attacker-influenced data, producing memory corruption that may be steered toward controlled reads/writes and ultimately arbitrary code execution. Because the vulnerable code path is reachable from a crafted HTML page and the CVSS vector carries S:C (scope changed), the flaw is assessed as crossing a security boundary - the compromise is not contained to the renderer sandbox but can reach code execution at the browser-process level, which is why the score is 9.6 despite requiring user interaction. CPE data (cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) confirms the affected product is Google Chrome, with the EUVD record pinning the boundary at builds earlier than 154.0.8037.92. The associated Chromium issue (issues.chromium.org/issues/560238698) and the stable-channel advisory are the authoritative technical references.
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:C/C:H/I:H/A:H
Remote crafted page (AV:N, PR:N) needs only a victim visit (UI:R); code executes outside the sandbox so scope changes (S:C) with full C/I/A impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Views in Google Chrome prior to 154.0.8037.92 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
Google Chrome desktop versions prior to 154.0.8037.92 are affected by a critical use-after-free vulnerability that could allow an unauthenticated remote attacker to execute arbitrary code outside the browser sandbox, potentially leading to full system compromise. Although no public exploit identified at time of analysis and the issue is not confirmed actively exploited, exploitation requires user interaction and overcoming sandbox escape complexity, meaning a successful attack could still result in significant data loss or lateral movement. Leadership should prioritize immediate patching given Chrome's widespread deployment and the critical severity of this flaw.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
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