Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
DeliveryPage abuses extensions resource exposure
-
ExploitBypass same-origin isolation
-
ExecutionRead cross-origin data
-
ImpactExfiltrate leaked data to attacker
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Resource sphere isolation
MITRE ATT&CK
1 technique across 1 tactic: Collection 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 or attacker-injected crafted HTML page in a vulnerable Chrome build prior to 155.0.8059.39 (UI:R), and the leak is scoped to Chrome's Extensions resource-exposure weakness rather than arbitrary cross-origin access; limiting factors are the required user interaction (visiting the page), the confidentiality-only, low-severity impact (C:L, I:N, A:N), and the narrow fixed-version window - users on 155.0.8059.39 or later are not affected. No elevated privileges or prior authentication are required (PR:N). |
| Impact | This is a genuine-but-moderate priority issue whose signals align consistently toward the lower end. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N, base 4.3) describes a network-reachable, low-complexity, unauthenticated flaw that nonetheless requires user interaction (victim must open a crafted HTML page) and yields only low confidentiality impact with no integrity or availability effect - consistent with the description of cross-origin data disclosure via Chrome's Extensions component. Chromium's own severity rating of Medium matches this. No EPSS score, no CISA KEV listing, and no public POC were provided in the intelligence, so per the data this is 'no public exploit identified at time of analysis' and there is no evidence of active exploitation. The absence of EPSS/KEV/POC is expected for a freshly disclosed browser Medium-severity bug and should not be read as a contradiction; it simply means exploitation likelihood cannot be quantified from the inputs. The main real-world driver of risk here is Chrome's enormous install base rather than the per-instance severity: a low-impact cross-origin leak is far less urgent than an RCE, but the ubiquity of the product warrants prompt patching. Verify affected-version detail with the vendor, as the EUVD version string ('Chrome 155.0.8059.39 <155.0.8059.39') is malformed/self-referential and only the fixed version (155.0.8059.39) is reliable. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing crafted HTML that abuses the improper resource exposure in Chrome's Extensions handling. When a victim running a pre-155.0.8059.39 Chrome build visits the page, the page reads data belonging to a different origin that should have been isolated, disclosing it to the attacker. No public exploit code was identified at the time of analysis, and the attack depends on the victim loading the malicious page (UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Cross-origin data exposure in Google Chrome before 155.0.8059.39 lets an unauthenticated remote attacker leak limited data from other origins by getting a victim to open a crafted HTML page that abuses an Extensions resource-exposure weakness. The issue is confidentiality-only and rated medium (CVSS 4.3, AV:N/AC:L/PR:N/UI:R/C:L/I:N/A:N), so exploitation depends on user interaction and yields only low-value data rather than code execution or integrity loss. No public exploit code was identified at time of analysis and CISA KEV does not list this CVE; a vendor patch is available in the 155.0.8059.39 stable release, and any user already on that build or later is not affected.
RemediationAI
Apply the vendor patch by updating Google Chrome to 155.0.8059.39 or later, which is the exact fixed version named in the Chrome stable channel advisory (https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html); on managed fleets push the corresponding MSI/PKG packages or rely on the browser's own updater, then fully quit and relaunch Chrome, since the new binary only takes effect after restart, and confirm the version under chrome://version or Menu > Help > About Google Chrome. Because the flaw lives in extension resource exposure, the only meaningful compensating control is to reduce the extension attack surface: use ExtensionInstallBlocklist or ExtensionSettings policies to allowlist only vetted extensions, and consider disabling unused or non-enterprise extensions, at the cost of breaking business or user workflows that depend on them - this is a partial mitigation, not a substitute for the upgrade. There is no practical server-side or network control that blocks the crafted HTML page itself, and the referenced Chromium issue (https://issues.chromium.org/issues/511796554) may be access-restricted, so rely on the vendor advisory for verification. Patch status: vendor-released patch version 155.0.8059.39; no public exploit code was identified at time of analysis.
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-668 (Exposure of Resource to Wrong Sphere): a resource inside Chrome's Extensions subsystem is reachable from a context that should not be able to read it, allowing cross-origin data to be observed rather than corrupted or executed. Chrome extensions expose resources such as manifests, scripts, stylesheets and packaged assets that are addressable through chrome-extension:// URLs; when the access checks or CORS-style gating on those resources are too permissive, a page from a different origin can cause them to be loaded and read back. The CVSS vector AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N describes a network-reachable flaw with no authentication barrier on the attacker's side, but with a mandatory victim action (opening the crafted page) and impact confined to low confidentiality loss, with no effect on integrity or availability and no privilege escalation or sandbox escape. The affected product per CPE data is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* - every Chrome build below the fixed train - and the EUVD record lists the affected range as versions earlier than 155.0.8059.39.
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:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Remote crafted page with no auth (AV:N/PR:N) but victim must load it (UI:R); only partial cross-origin data leak, so C:L with no integrity or availability impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Improper resource exposure in Extensions in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to obtain cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
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.
EUVD-2026-93704
GHSA-c3mg-5gv5-w6h4
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB