Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious page
-
DeliveryDeliver crafted content triggering CWE-706
-
ExploitWin timing/state race (AC:H)
-
ExecutionCross scope boundary (S:C)
-
ImpactExecute code / access protected data
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Incorrectly specified target
|
| Exploitation Conditions | Exploitation requires the victim to actively load attacker-controlled web content in Chrome before version 154.0.8037.57 (UI:R - user interaction such as visiting a malicious page). The high attack complexity (AC:H) indicates additional non-trivial prerequisites such as specific timing, memory grooming, or a race condition to reliably trigger the incorrectly-resolved name/reference (CWE-706). No authentication or elevated privileges are needed (PR:N). Limiting factors: mandatory user interaction, high complexity reducing reliability, and the fix already shipping in the stable channel - patched or auto-updated browsers are not exposed. |
| Impact | The CVSS 3.1 base score is 8.3 (High) with vector AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H - network-reachable, unauthenticated, but requiring user interaction (UI:R, i.e. visiting a malicious page) and high attack complexity (AC:H, implying grooming/timing/race conditions). The scope change (S:C) combined with full C:H/I:H/A:H impact is consistent with a sandbox-escape-class or cross-origin/cross-context break rather than a renderer-contained bug, which is the primary reason the score exceeds the AC:H penalty. No EPSS score, no CISA KEV listing, and no public exploit code are present in the input, so this is 'no public exploit identified at time of analysis' - a real defensive priority given the ubiquity of Chrome, but not evidence of active exploitation. Two data-quality tensions should be flagged: (1) the sole tag 'Information Disclosure' contradicts the vector's I:H/A:H, meaning this is not merely a disclosure bug; and (2) no description is provided, so CWE-706 (Use of Incorrectly-Resolved Name or Reference) and chromium issue 513403696 are the only technical anchors. Overall this is a genuine high-priority patch-now issue for any Chrome fleet, but the AC:H and UI:R metrics meaningfully lower the likelihood of trivial mass exploitation versus an AC:L/UI:N flaw. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page and lures a victim into visiting it (UI:R). The page triggers an incorrectly-resolved name/reference condition (CWE-706) under specific timing or state conditions (AC:H), causing a scope-crossing compromise that yields code execution or cross-context data access with full confidentiality, integrity, and availability impact. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Sep 29, 2026
Google Chrome versions prior to 154.0.8037.57 contain an incorrectly-resolved name or reference flaw (CWE-706) that remote, unauthenticated attackers can trigger by convincing a user to load attacker-controlled web content; the issue is rated CVSS 3.1 8.3 High with scope change (S:C) and high confidentiality, integrity and availability impact. Exploitation is gated by mandatory user interaction (UI:R) and high attack complexity (AC:H), requiring non-trivial prerequisites such as specific timing, memory grooming or a race condition, and no public exploit code has been identified at time of analysis. Google has already shipped a stable-channel fix in Chrome 154.0.8037.57, so patched or auto-updated browsers are not exposed.
Earlier versions of this analysis (1)
Google Chrome desktop builds that predate the September 2026 stable channel update can be induced to mishandle attacker-influenced web content, meaning a user who navigates to a malicious or compromised page on an unpatched browser is the exposure path. The defect class, affected component, and severity are undocumented in the available intelligence - there is no description, no CVSS score or vector, no CWE, and no EPSS probability - so impact cannot be quantified beyond that standard browser threat model. Vendor-released fixes have shipped in the Chrome stable channel, and no public exploit code has been identified at time of analysis; environments with auto-update enabled are protected as the update rolls out.
RemediationAI
The primary fix is to upgrade Google Chrome to 154.0.8037.57 or later, as released in the stable channel documented at http://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0856730748.html (tracked upstream at https://issues.chromium.org/issues/513403696); vendor-released patch: 154.0.8037.57. Desktop installations that auto-update and are relaunched after updating are no longer exposed, so administrators should confirm the applied version rather than assume the background update completed, since a pending update that has not been relaunched leaves the running browser vulnerable. Ubuntu and other distribution users should apply the corresponding Chromium/Chrome package update issued by their vendor, since the vulnerability was reported through vendor:ubuntu. Where immediate upgrading is not possible, compensating controls carry real trade-offs: enforce enterprise update and relaunch policies so stale builds cannot persist, restrict browsing to trusted, allow-listed sites and block untrusted web content to reduce the chance of the required user interaction, and consider disabling or tightly restricting optional high-risk browser features until the build is updated. These are partial mitigations only, since the flaw requires no authentication and can be reached from ordinary web pages; the reliable remedy remains upgrading to 154.0.8037.57 or later.
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-706, Use of Incorrectly-Resolved Name or Reference, meaning the affected code resolves a name, handle or reference to the wrong object instead of the intended one. In a browser engine this class of defect commonly manifests as a mismatch between the object the code believes it is operating on and the object it actually reaches, which can lead to type confusion, out-of-bounds access or exposure of data belonging to a different origin or process. The assessed vector (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) describes a network-reachable, unauthenticated defect that nonetheless demands user interaction and high-complexity trigger conditions such as precise timing, heap grooming or a race, yet achieves impact that crosses a security scope boundary (S:C) with high confidentiality, integrity and availability consequences. The CWE-706 classification is consistent with the EUVD 'Information Disclosure' tag, while the scope change and high integrity/availability ratings indicate the incorrect resolution is not limited to a pure read of data. Affected code ships in the Google Chrome stable channel; the EUVD data lists Chrome builds below 154.0.8037.57, and Ubuntu is credited via the vendor:ubuntu reporting channel, implying downstream Chromium packaging is also in scope where it tracks the same codebase.
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:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Network-delivered via malicious page (AV:N/UI:R), no auth (PR:N), high complexity for reliable triggering (AC:H), and a scope-crossing full-impact compromise (S:C, C/I/A:H).
Primary rating from Vendor (vendor:ubuntu).
CVSS VectorVendor: vendor:ubuntu
Lifecycle Timeline
2DescriptionCVE.org
[Unknown description]
Executive ViewAI
Google Chrome releases prior to 154.0.8037.57 carry a high-severity browser flaw (CVE-2026-95334) that can let a remote attacker gain broad control over data and system resources on any machine where a user is lured into opening crafted web content. Because Chrome is deployed across virtually the entire workforce, any unpatched endpoint represents an organizational exposure rather than an isolated technical issue, though exploitation requires a successful user-interaction chain and non-trivial timing conditions. Leadership should treat this as a routine patch-management priority with a defined remediation deadline, not as an emergency incident.
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
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
Vendor 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 |
EUVD-2026-89150
GHSA-mvf9-p63r-q35f
NVD
CVE.org
EPSS
Exploit-DB