EUVD-2026-89226
GHSA-cwfr-wpgr-4mj9
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted content to victim
-
DeliveryVictim opens/interacts in Chrome
-
ExploitTrigger use-after-free on freed object
-
ExecutionReclaim memory with controlled data
-
ImpactExecute arbitrary code in renderer
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 or interact with attacker-crafted content in Google Chrome (UI:R) on a version below 154.0.8037.57; the supplied vector specifies a LOCAL attack vector (AV:L), implying the triggering content is reached through a local flow (e.g., an opened file or local rendering context) rather than pure remote drive-by, though the exact feature cannot be confirmed because the description is unavailable. No authentication is required (PR:N). Limiting factors: mandatory user interaction, the AV:L local-access constraint as scored, scope-unchanged (S:U) confinement to the exploited process, and that patched builds (>=154.0.8037.57) are not affected. If the underlying bug is in fact remotely web-reachable, the practical exposure would be higher than the AV:L score suggests - verify against Chromium issue 520516206. |
| Impact | This is a CWE-416 use-after-free in Google Chrome (fixed in the stable-channel desktop update, EUVD-2026-89226; affected builds below 154.0.8037.57). The vendor-supplied CVSS 3.1 vector is AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H = 7.8, indicating a LOCAL attack vector with required user interaction and full compromise of confidentiality, integrity and availability - an RCE-class memory-corruption bug. There is no EPSS score, no CISA KEV listing, and no public exploit provided in the input, so exploitation status is: no public exploit identified at time of analysis. Note a signal tension worth verifying: most browser UAFs of this class (and the sibling CVEs in this same Chrome release) are scored AV:N (drive-by via a malicious web page), yet this record carries AV:L - this may reflect a component reachable only via a locally opened file or a specific local flow, OR it may be a scoring inconsistency in the source. The description is unavailable, so the exact triggering surface cannot be confirmed from the input; the AV:L vs. AV:N distinction should be verified against the Chromium issue (520516206) and Google advisory before final prioritization. Despite missing EPSS/KEV data, Chrome's ubiquity and the historical reliability of UAF-to-RCE exploitation in the renderer keep this a genuine patch-now item; it is not a high-CVSS-but-low-real-risk case. |
| Exploit ScenarioDerived | An attacker crafts malicious web content (or a local file rendered by Chrome) that manipulates object lifetimes to trigger the use-after-free; when a victim opens or interacts with the content, the freed object is reclaimed with attacker-controlled data, yielding memory corruption and likely code execution in the renderer. User interaction (UI:R) is required and, per the supplied vector, a local vector (AV:L). No public proof-of-concept is present in the provided data. |
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 prior to 154.0.8037.57 lets an attacker who convinces a user to open or interact with crafted content trigger the reclamation and subsequent dereference of a freed object, yielding high confidentiality, integrity, and availability impact within the affected process (CVSS 3.1 base 7.8). The assessed vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates no authentication is required but that user interaction is mandatory and that the scored attack path is local rather than a pure remote drive-by; if the underlying bug proves remotely web-reachable, real-world exposure would be higher than the AV:L score implies. Vendor-released patched builds exist (154.0.8037.57 and later, stable-channel desktop update tracked as EUVD-2026-89226), and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Earlier versions of this analysis (1)
CVE-2026-95298 is an unenriched record attributed to the Ubuntu vendor CNA that currently carries no description, no CVSS vector, no CWE classification, and no CPE data, so neither the technical nature of the flaw nor its blast radius can be determined. Because no affected product, package, or version range has been published, it is impossible to state whether the issue is remotely or locally reachable, whether it requires authentication, or whether it is triggered in a default configuration. Exploitation status: no public exploit identified at time of analysis, although this reflects an absence of published data rather than a confirmed negative. Risk cannot be meaningfully assessed from the available data, and no remediation decision should be made until the record is enriched from an authoritative source.
RemediationAI
Upgrade to Google Chrome 154.0.8037.57 or later; this is a vendor-released patch and the fix is distributed through the stable-channel desktop update described at http://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0856730748.html, with the underlying defect documented at https://issues.chromium.org/issues/520516206. Because Chromium-based packages are maintained downstream, Ubuntu users should apply the corresponding distribution update (the vendor is listed as the reporter) rather than relying only on an upstream binary swap, and should confirm the running version after restarting the browser, since Chromium-based browsers often keep the old binary resident until all processes exit. If immediate upgrade is not possible, reduce the attack surface while accepting functional trade-offs: constrain browsing to trusted sites and avoid opening untrusted documents or locally saved HTML content in Chrome, since the scored prerequisite is user interaction routed through a local (AV:L) path, and consider forcing stricter site isolation and disabling unnecessary local file rendering or extension privileges, understanding that these are partial mitigations that do not remove the use-after-free and may break legitimate workflows. There is no reliable way to mitigate a memory-corruption primitive of this class at the network edge, so patching remains the only complete remediation; note that no public exploit code has been identified, so urgency is driven by the 7.8 severity and the trivial user-interaction requirement rather than by observed exploitation.
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 class is CWE-416 (Use After Free), a classic memory-safety defect in which an object is freed while a stale reference to it remains live; a subsequent read or write through that dangling pointer produces information disclosure or arbitrary memory corruption. In Chromium, such objects are typically allocated and reclaimed by the browser's partitioning allocator inside a renderer or other sandboxed child process, and exploitation normally requires an attacker to first trigger the faulty lifetime transition and then shape the heap so the freed slot is reoccupied with attacker-influenced data. The affected component is not identified in the available data because the CVE has no description; the authoritative pointer is Chromium issue 520516206, which is where the precise subsystem (for example a V8, Blink, or graphics-layer object) must be confirmed. The supplied CPE/version data scopes the flaw to Google Chrome builds below 154.0.8037.57, and the Ubuntu vendor report indicates that distribution-packaged Chromium builds derived from that upstream release stream inherit the defect. Because the assessed vector is scope-unchanged (S:U), any successful exploit is expected to remain confined to the compromised process rather than immediately crossing a privilege boundary, but that confinement should be treated as the reason the score is 7.8 rather than a guarantee of containment once a full exploit chain is developed.
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:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Retaining vendor AV:L and UI:R since no description contradicts them; UAF gives full C/I/A impact with no auth (PR:N) and process-confined S:U.
Primary rating from Vendor (vendor:ubuntu).
CVSS VectorVendor: vendor:ubuntu
Lifecycle Timeline
1DescriptionCVE.org
[Unknown description]
Executive ViewAI
A use-after-free memory corruption flaw in Google Chrome desktop builds prior to 154.0.8037.57 could allow an attacker who convinces a user to open or interact with crafted content to crash or seize control of that user's browser session, with high impact to confidentiality, integrity, and availability of data handled in the browser. Chrome is deployed across virtually every knowledge worker on managed Windows, macOS, and Linux endpoints, so the affected population is effectively the entire workforce and the sensitive data reachable through their browser sessions. No public exploit code or confirmed active exploitation has been identified at time of analysis, making this a patch-before-exploitation priority rather than an active incident.
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.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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 Information Disclosure
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