Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious HTML page exploiting DOMStorage
-
DeliveryDeliver URL via phishing or malvertising
-
ExploitVictim loads page in unpatched Chrome
-
ExecutionOrigin validation check bypassed in DOMStorage
-
PersistRead target-origin localStorage or sessionStorage data
-
ImpactExfiltrate harvested data to attacker
Vulnerability Assessment
| Weakness |
CWE
|
| Exploitation Conditions | Exploitation requires the victim to actively visit a crafted HTML page in an unpatched Chrome browser (UI:R per CVSS), making phishing or social engineering the primary delivery mechanism. The vulnerability exists in Chrome's DOMStorage component without any non-default configuration requirement - all standard Chrome deployments prior to 151.0.7922.72 are susceptible. No server-side configuration is needed. Limiting factors: the attack cannot be automated at scale (SSVC: not automatable), impact is bounded to cross-origin confidentiality disclosure (no code execution, no integrity or availability impact), and the victim must be directed to and must load the attacker-controlled page. CVSS PR:N confirms no authentication to any service is required from the attacker's side. |
| Impact | The CVSS 3.1 base score of 4.3 (Medium) reflects a network-reachable (AV:N), low-complexity (AC:L), unauthenticated (PR:N) attack that nonetheless requires mandatory user interaction (UI:R) and yields only limited confidentiality impact (C:L) with no scope change (S:U), integrity, or availability consequences. EPSS at 0.17% (7th percentile) signals minimal observed exploitation pressure across the threat landscape. SSVC corroborates this: exploitation status is none, the attack is not automatable, and technical impact is only partial. No KEV listing and no public exploit code further reduce urgency. This is a genuine but low-priority finding - real-world risk is constrained by the user-interaction requirement and the bounded impact of cross-origin storage disclosure rather than code execution. |
| Exploit ScenarioDerived | An attacker crafts a malicious HTML page containing JavaScript that exploits the DOMStorage origin validation flaw, then delivers the link via phishing, malicious advertising, or a compromised website. When the victim visits the page in an unpatched version of Chrome, the script reads localStorage or sessionStorage data scoped to a different origin - potentially harvesting session identifiers, cached user data, or application state stored by a target web service. No public exploit code is known at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 30, 2026
Cross-origin data leakage in Google Chrome's DOMStorage component (versions prior to 151.0.7922.72) permits a remote attacker to read storage data belonging to a different origin by luring a victim to a crafted HTML page. The flaw is rooted in an origin validation error (CWE-346) within the DOMStorage subsystem, violating same-origin policy enforcement. EPSS is very low at 0.17% (7th percentile), no active exploitation is confirmed, and Chromium itself rates this Low severity, placing this in the lower tier of browser security issues despite its network-reachable attack surface.
RemediationAI
Update Google Chrome to version 151.0.7922.72 or later, which resolves the DOMStorage origin validation flaw as documented in the stable channel advisory at http://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Chrome's auto-update mechanism handles this for most consumer deployments; enterprise administrators using managed Chrome deployments (via policy or browser management platforms) should verify version propagation. No documented workaround exists for this specific issue - disabling JavaScript would prevent exploitation but renders most web applications non-functional and is not a practical compensating control. The primary and only recommended remediation is applying the vendor patch.
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
DOMStorage encompasses the Web Storage API's localStorage and sessionStorage mechanisms, which browsers use to persist key-value data strictly scoped to a given origin. CWE-346 (Origin Validation Error) indicates that Chrome's implementation incorrectly validates or enforces the origin boundary when accessing DOMStorage entries, enabling a cross-origin read. The affected component is the Google Chrome browser itself (CPE: cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) for all versions preceding 151.0.7922.72. The attack is entirely client-side - the browser is the vulnerable endpoint, not any web server.
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
Sources disagree (Low–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Network-delivered crafted page requires victim interaction (UI:R); impact limited to cross-origin storage read with no integrity, availability, or scope-change consequence.
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: Chrome
Lifecycle Timeline
3DescriptionCVE.org
Inappropriate implementation in DOMStorage in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Low)
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.
Related Vulnerabilities in Google Chrome 151 Security Vulnerabilities
View all 80Same weakness CWE-346 – Origin Validation Error
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
EUVD-2026-50859
GHSA-jgx6-h6w9-gqh9
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB