EUVD-2026-89233
GHSA-h766-m59c-v6j3
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessVictim visits attacker-controlled page
-
DeliveryMalicious script triggers use-after-free
-
ExploitReclaim freed object to corrupt memory
-
ExecutionAchieve arbitrary code execution in renderer
-
ImpactChain sandbox escape for host compromise
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 a malicious or compromised web page in a vulnerable Chrome desktop build earlier than 154.0.8037.57 (UI:R user interaction is the primary limiting factor). No authentication or prior privileges are needed (PR:N). Because scope is unchanged (S:U), the flaw yields code execution confined to the renderer/sandboxed process; full host compromise realistically requires chaining a separate sandbox-escape vulnerability. Applies to default configurations - no special feature toggle is documented, though the exact vulnerable component is undisclosed. |
| Impact | This is a genuine high-priority issue driven by the affected product's ubiquity rather than by confirmed exploitation. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) describes a network-reachable, low-complexity, unauthenticated use-after-free requiring only that the victim visit a malicious page (UI:R). Impact is full CIA compromise within the renderer's security scope (S:U - no sandbox escape claimed here). No EPSS score is provided, the CVE is NOT in CISA KEV, and no public POC is referenced - so exploitation status is: no public exploit identified at time of analysis. There is no conflict between the vector and the (absent) description: memory-corruption UAFs of this class are the standard Chrome browser-exploitation primitive, and the S:U scope means this alone yields renderer code execution, typically chained with a separate sandbox-escape bug for full RCE. The key missing signal is the description itself ('[Unknown description]'), so the specific vulnerable component/feature cannot be confirmed from the input - only that a patch exists in Chrome 154.0.8037.57. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page (or compromises an ad/iframe on a legitimate site) that drives a specific Blink/V8/component operation into a use-after-free condition. When a victim running a pre-154.0.8037.57 Chrome visits the page, the freed-then-reused object grants the attacker a memory-corruption primitive leading to arbitrary code execution in the renderer process. No public POC is referenced, but UAF renderer bugs are routinely weaponized and this would typically be paired with a sandbox-escape to achieve host compromise. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Sep 29, 2026
Use-after-free memory corruption in Google Chrome desktop builds earlier than 154.0.8037.57 (CWE-416) allows remote attackers to corrupt memory and potentially achieve code execution inside the renderer process when a victim opens a malicious or compromised web page. The flaw is remotely reachable with low attack complexity and no privileges required (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8), but it hinges on user interaction and, because scope is unchanged, exploitation is contained to the sandboxed renderer; full host compromise realistically requires chaining a separate sandbox-escape bug. There is no confirmed active exploitation and no public exploit identified at time of analysis, so the elevated priority is driven by Chrome's ubiquity and the reliability of memory-safety bugs in this class rather than by observed attacks; vendor patches are already available.
Earlier versions of this analysis (1)
Google Chrome desktop stable-channel builds are affected by an unspecified security flaw addressed in Google's September 2026 stable channel update, but the impact, attack vector, and severity cannot be determined from available intelligence because no description, CVSS score or vector, or CWE was published. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, while an EPSS score is not available; exploitation is constrained to unpatched installations given that a vendor fix already exists. Affected parties include organizations running unpatched Chrome desktop and downstream distributions such as Ubuntu that repackage the upstream Chromium codebase.
RemediationAI
Vendor-released patch: upgrade Google Chrome to 154.0.8037.57 or later. On managed desktops this is done through chrome://settings/help or the enterprise update policy (Google Update) with a forced restart of the browser - an updated binary is not effective until every running Chrome process is restarted, so schedule a mandatory relaunch rather than relying on background updates. Ubuntu and other downstream Chromium consumers should apply the corresponding distribution security update from vendor:ubuntu rather than mixing an upstream tarball with a packaged browser. No public exploit code has been identified, so emergency change windows are not strictly required, but the ubiquity of the target justifies prioritizing the upgrade on internet-facing or browsing-heavy endpoints. Where immediate upgrading is not possible, compensating controls should focus on containing the renderer rather than on generic hardening: verify that the Chrome sandbox and Site Isolation remain enabled (disabling them with --no-sandbox or equivalent makes a renderer-hosted use-after-free far more dangerous), restrict browsing to trusted origins via URL blocklists or enterprise policy, and consider disabling third-party extensions that inject into renderer content, accepting the productivity trade-off. Because the assessed scope is unchanged, an attacker still needs a separate sandbox-escape chain for host-level code execution, so keeping OS-level mitigations (ASLR, seccomp, per-OS browser sandboxing) intact materially reduces the ceiling of this bug; blockloading untrusted pages in privileged or high-value profiles is a practical short-term risk reduction with the side effect of restricting user workflow. Consult the Chrome Releases advisory (http://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0856730748.html) and the Chromium issue 553130481 for the definitive fixed build and any subsequent detail disclosure.
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 CWE-416, a use-after-free, in the Google Chrome browser engine - the affected component is not disclosed by the vendor at the time of the advisory, a standard practice until a majority of the user base has updated. Use-after-free arises when the browser frees a heap object (typically a DOM node, V8 object, or IPC-bound structure) but retains a dangling reference that an attacker can force the code to dereference again, yielding a controllable read/write primitive; in Chrome's multi-process model this occurs inside the sandboxed renderer, which is why the assessed impact is high confidentiality, integrity, and availability (C:H/I:H/A:H) yet scope-unchanged (S:U). The advisory data maps this to the Chrome desktop stable channel and references the Chromium issue tracker entry 553130481 and the Chrome Releases stable-channel advisory; the EUVD entry (EUVD-2026-89233) records affected Chrome builds below 154.0.8037.57, and the Ubuntu security team is listed as a reporter, indicating downstream Chromium/Chrome packaging in Ubuntu is also in scope. Tags of Information Disclosure, Use After Free and Memory Corruption are consistent with a dangling-pointer primitive that can leak memory and corrupt heap state before escalating to code execution within the renderer. No CPE strings were supplied in the source data, so affected-platform scoping relies on the Chrome stable release channel and the EUVD version range rather than on formal CPE identifiers.
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
Web-delivered UAF needs only a page visit (AV:N/AC:L/PR:N/UI:R); renderer-scoped memory corruption gives full C/I/A with no confirmed sandbox escape (S:U).
Primary rating from Vendor (vendor:ubuntu).
CVSS VectorVendor: vendor:ubuntu
Lifecycle Timeline
2DescriptionCVE.org
[Unknown description]
Executive ViewAI
Google Chrome desktop builds earlier than 154.0.8037.57 contain a use-after-free memory corruption flaw that a remote attacker can trigger simply by getting an employee to open a malicious or compromised web page, potentially leading to code execution inside the browser's renderer process. Because Chrome is deployed broadly across the workforce, any unpatched endpoint represents an exposed path that requires only routine web browsing to reach, though exploitation is constrained to the sandboxed renderer and would require a separate escape to compromise a full host. Leadership should treat this as a patch-management priority driven by the ubiquity of the product rather than by evidence of active attacks, since no public exploit has been identified at the time of analysis.
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.
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
Same weakness CWE-416 – Use After Free
View allSame technique Use After Free
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Exploit-DB