Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent network position
-
DeliveryDeliver crafted content to victim
-
ExploitVictim interaction loads page in vulnerable Chrome
-
ExecutionTrigger externally-controlled cross-sphere reference
-
ImpactDisclose or corrupt sensitive browser data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V4 - API and Web Service External resource reference control
|
| Exploitation Conditions | Exploitation requires the attacker to hold an adjacent network position (CVSS AV:A - same local/L2 network segment such as a shared LAN or Wi-Fi, not arbitrary internet reach) AND the victim to be running a Google Chrome desktop build earlier than 154.0.8037.57. User interaction is required (UI:R): the victim must load or navigate to attacker-influenced content. No authentication or elevated privileges are needed (PR:N). Limiting factors: the adjacent-only vector and the mandatory user interaction substantially constrain mass or remote exploitation; an official fix is already shipped in the stable channel, so exposure is limited to unpatched clients. The exact triggering feature could not be named because the CVE description was not provided. |
| Impact | Risk is driven primarily by prevalence rather than exploitation signals. The affected product is Google Chrome desktop (fixed in 154.0.8037.57), one of the most widely deployed applications in existence, so the potential exposure is enormous. However, the exploitation-likelihood signals are quiet: there is no CISA KEV listing, no EPSS score provided, and no public POC identified in the input. The vendor CVSS 3.1 vector (AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.0) contains a notable anomaly - AV:A (Adjacent) rather than the AV:N typical of browser rendering bugs. This implies the attacker must occupy the same local/adjacent network segment (same L2 broadcast domain, shared Wi-Fi/LAN) rather than exploit arbitrarily from the internet, which materially narrows the realistic attacker population despite the high base score. The CWE-610 (Externally Controlled Reference to a Resource in Another Sphere) classification is consistent with a cross-sphere reference leaking or corrupting data, but the 'Information Disclosure' tag conflicts with the vector's C:H/I:H/A:H, which claims full confidentiality, integrity AND availability impact - the tag understates the flaw. The underlying CVE description was not available ('[Unknown description]'), so the exact mechanism cannot be confirmed. Net: a high-CVSS bug in a ubiquitous product, but with adjacent-only reach, required user interaction, an available patch, and no evidence of active or imminent exploitation - a patch-on-normal-cadence priority, not an emergency, absent new exploitation intelligence. |
| Exploit ScenarioDerived | An attacker on the same local network (e.g., shared corporate LAN or public Wi-Fi) lures a victim running a pre-154.0.8037.57 Chrome build into visiting or loading attacker-influenced content that triggers an externally controlled reference to a resource in another sphere. The user interaction requirement (UI:R) means the victim must open a page or perform a navigation. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Sep 30, 2026
Information disclosure in Google Chrome desktop builds earlier than 154.0.8037.57 lets an attacker who shares a local network segment with the victim trigger a flaw that the assessed CVSS scores as high impact across confidentiality, integrity, and availability (CVSS 8.0, AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). The attacker needs no authentication or elevated privileges (PR:N), but must be positioned on the same adjacent L2 segment as the target (AV:A) and must get the victim to load attacker-influenced content (UI:R) - a combination that substantially constrains mass or opportunistic exploitation. An official fix is already available on the stable channel and no public exploit code has been identified at time of analysis, so risk here is driven primarily by Chrome's ubiquity and by unpatched client exposure rather than by observed exploitation activity.
Earlier versions of this analysis (1)
Google Chrome desktop builds are affected by a security flaw for which the vendor has shipped a fix, but no CVE description, CVSS score, or CWE classification has been published at the time of analysis. Because the only available reference is a Chrome stable channel release announcement and the reporting source is a distribution vendor (Ubuntu), this entry should be treated as a placeholder advisory rather than a fully characterized vulnerability; exploitation prerequisites, attack vector, and impact cannot be confirmed from the available data. Based on the product identity, successful exploitation almost certainly requires the victim to run an unpatched Chrome desktop build and to render attacker-controlled web content, making user interaction through navigation the primary limiting factor. No public exploit code has been identified at time of analysis, the flaw is not listed on CISA KEV, and no EPSS score was supplied.
RemediationAI
Apply the vendor-released patch by upgrading Google Chrome to 154.0.8037.57 or later - released through the stable channel as documented in the Chrome release advisory (http://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0856730748.html) - and verify the running build via chrome://version or the About Chrome dialog, remembering that the update only takes effect after the browser is fully restarted. Managed fleets should confirm that Google Update or Chrome Browser Cloud Management is not pinned below the fixed build, and Ubuntu/Linux users should update through the vendor channel noted in the report (vendor:ubuntu) rather than relying on a third-party repackaging. If immediate upgrade of some clients is not possible, account for the AV:A requirement as the cheapest compensating control: treat untrusted L2 segments as hostile by segmenting guest Wi-Fi and untrusted VLANs away from browsers that handle sensitive sessions, which reduces the pool of hosts an attacker can launch from, at the cost of reduced access to legitimate local network resources and no actual removal of the flaw. Detecting the issue through network inspection is not practical here because the triggering feature is not identified in the available data, so monitoring should focus on patch compliance; there is no evidence of public exploit code at time of analysis, so prioritization should be driven by prevalence of unpatched Chrome clients rather than by exploitation urgency.
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-610, Externally Controlled Reference to a Resource in Another Sphere: one party supplies a reference (a URL, path, origin, or resource identifier) that the application resolves in a security context or sphere it was never intended to reach, crossing a trust boundary and yielding access to data or functionality beyond what the caller should influence. In a browser this class typically surfaces when network-influenced content causes Chrome to resolve such a reference against a privileged or unrelated context - the sort of boundary that Chrome's multi-process sandbox and site isolation are designed to enforce. The assigned vector, AV:A, is unusual for a desktop browser: rather than arbitrary internet reach, the attacker must hold a position on the same local/L2 network as the victim (shared LAN or Wi-Fi), which suggests the triggering path depends on content or responses reachable over that adjacent segment rather than on a public web page, and UI:R means the victim must navigate to or load that content before the flaw fires. The specific component or feature involved cannot be named from the available data because no CVE description was supplied; the authoritative technical record is the Chromium issue tracker entry 513134076, and EUVD-2026-89257 records the affected range as Chrome builds below 154.0.8037.57. No CPE strings were provided with this record.
Know when the next one hits your stack
- 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:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Retains vendor AV:A (adjacent-only reach) and UI:R (victim must load content); PR:N as no auth implied; full C/I/A:H per vendor impact absent a description contradicting it.
Primary rating from Vendor (vendor:ubuntu).
CVSS VectorVendor: vendor:ubuntu
Lifecycle Timeline
2DescriptionCVE.org
[Unknown description]
Executive ViewAI
Google Chrome desktop versions prior to 154.0.8037.57 contain a high-severity vulnerability (CVE-2026-95376) that could enable an attacker on the same local network to access sensitive information, modify system data, or cause disruptions when a user loads malicious content. This affects all unpatched Chrome desktop users across the organization, and while exploitation requires the attacker to be on the same network and a user to interact with malicious content, the widespread use of Chrome makes prompt patching essential to protect organizational assets and maintain business continuity.
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
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Same 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 |
EUVD-2026-89257
GHSA-9386-qgfg-gg42
NVD
CVE.org
EPSS
Exploit-DB