EUVD-2026-89390
GHSA-3qr6-vrrv-wjp4
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
DeliveryTrigger use-after-free in Views
-
ExploitReclaim freed object to corrupt memory
-
ExecutionEscape renderer 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 | Exploitation requires the victim to open an attacker-controlled crafted HTML page in a vulnerable Chrome desktop build prior to 154.0.8037.92 (UI:R - user interaction via social engineering is mandatory, which is the primary limiting factor). No authentication or prior privileges are needed (PR:N), and no non-default configuration is required - a stock Chrome installation is affected. The vulnerability yields a sandbox escape (S:C), so successful exploitation is not confined to the renderer. Limiting factors: the mandatory user interaction (visiting the page) and the availability of a vendor patch that closes the window. |
| Impact | This is a genuinely high-priority vulnerability, not a CVSS-inflated one. The vendor vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H (9.6) describes a network-reachable, low-complexity, unauthenticated use-after-free that achieves a scope change (S:C) - consistent with the description's key phrase 'execute arbitrary code outside the sandbox,' meaning a full renderer-sandbox escape rather than a contained renderer compromise. Signals partly conflict on urgency: CISA SSVC records Exploitation: none and Automatable: no, and there is no CISA KEV entry and no public POC, so there is currently no evidence of active exploitation or mass scanning. However, SSVC Technical Impact: total aligns with the S:C/C:H/I:H/A:H rating and confirms the worst-case impact is complete. The one mitigating factor is UI:R - the victim must be socially engineered into visiting a crafted HTML page - which is why Automatable is 'no.' Net: exploitation is not yet observed, but given Chrome's ubiquity, the sandbox-escape class, and available patch, this warrants prompt patching. |
| Exploit ScenarioDerived | An attacker crafts a malicious HTML page that triggers a use-after-free in the Views UI component and lures a victim (via phishing, malvertising, or a compromised link) into opening it in an unpatched Chrome build below 154.0.8037.92. Successful exploitation frees and reclaims an object to corrupt memory, escaping the renderer sandbox to run arbitrary code on the host. No public exploit code is identified at time of analysis, and CISA SSVC lists exploitation status as none. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 29, 2026
Use-after-free in Chrome's Views UI framework allows a remote attacker who convinces a victim to open a crafted HTML page to execute arbitrary code outside the browser sandbox on any Chrome desktop build prior to 154.0.8037.92. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, 9.6) confirms remote, unauthenticated attack with no special privileges, but also confirms that user interaction - social engineering to get the victim to load the page - is mandatory, which is the main limiting factor; the scope change (S:C) reflects that impact is not confined to the renderer. No public exploit was identified at the time of analysis and CISA's SSVC assessment rates exploitation as 'none' and not automatable, but a vendor patch is available from Google and the technical impact is total, making prompt updating the priority.
RemediationAI
Vendor-released patch: Chrome 154.0.8037.92 - upgrade to that version or later, which Google documents in the September 2026 stable channel advisory at https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_01807488085.html; on managed fleets force it via the Chrome Browser Cloud Management update policy or your OS package channel (MSI/DEB/RPM), and note that Chrome only applies the fix after a full browser restart, so a lingering session keeps the vulnerable Views code live. Because exploitation requires the victim to open an attacker-controlled HTML page (UI:R), the practical interim control is to keep untrusted browsing confined to already-updated builds and to treat unpatched Chrome instances as unacceptably exposed for high-risk users such as administrators, developers, and anyone handling secrets - a trade-off that is workable only for short windows and does not survive ordinary web browsing habits. Standard browser hardening does not compensate: the bug is in the browser-process Views layer, so renderer sandboxing, site isolation, and strict extension policies do not block the escape, and blocking scripts or JavaScript via policy would degrade most sites without reliably preventing a Views code path from being reached, so it should be treated as a last resort for narrow, time-boxed cases rather than an alternative to patching. No workaround equivalent to the fix is described in the available references, and there is no public exploit code identified at the time of analysis, so the risk window is driven mainly by patch deployment speed.
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
Views is Chromium's C++ UI toolkit that renders the browser's own chrome (toolbars, bubbles, dialogs, menus, permission prompts) in the browser process rather than in a sandboxed renderer, so memory-safety bugs there sit on the privileged side of the browser's security boundary. The root cause here is CWE-416, use-after-free: an object is released while a dangling reference to it is still reachable, so a later access or virtual call operates on memory that may have been reallocated with attacker-influenced content, giving a path to controlled memory corruption. Because the flaw is in Views rather than in Blink/V8, the standard renderer sandbox and site isolation do not contain the consequence - the CVSS scope-change component (S:C) and the 'outside the sandbox' wording in the advisory both reflect that a successful exploit escapes the renderer boundary. The CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* is broad and does not itself encode a version, but Google's advisory and ENISA EUVD-2026-89390 scope the issue to Chrome builds below 154.0.8037.92 across desktop platforms; the associated tags (RCE, memory corruption, denial of service) are consistent with a UAF that can be steered either to code execution or to a crash.
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
Network-reachable via a crafted page with no privileges (PR:N) but required user interaction (UI:R); the described sandbox escape justifies S:C and 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)
Articles & Coverage 1
Executive ViewAI
Google Chrome desktop builds prior to 154.0.8037.92 are affected by a critical use-after-free in the Views UI framework that can allow a remote, unauthenticated attacker to execute arbitrary code outside the browser sandbox if a user opens a crafted HTML page. Because Chrome is widely deployed across the workforce, a successful social-engineering lure could compromise individual workstations and potentially expose corporate data or credentials, making this an urgent fleet-wide patch management issue. There is no public exploit identified at time of analysis, and CISA rates exploitation as none and not automatable, but the vendor-released patch: 154.0.8037.92 is available and should be prioritized.
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