Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker crafts malicious HTML page exploiting Cast input handling
-
ExploitVictim navigates to attacker-controlled page in unpatched Chrome
-
ExecutionCrafted input bypasses Cast validation, violating same-origin policy
-
ImpactCross-origin data leaked to attacker-controlled page context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Exploitation requires the victim to actively visit an attacker-controlled or compromised HTML page using Google Chrome prior to version 151.0.7922.72 on a desktop platform - the CVSS UI:R metric confirms this user interaction is mandatory and cannot be bypassed. The Cast component must be active, which is the default configuration in Chrome desktop; no non-default configuration is required to be vulnerable. PR:N confirms no authentication or session privileges are needed from the attacker's side. Exploitation is limited to desktop Chrome installations (per CPE scope); the impact ceiling is limited cross-origin data disclosure (C:L) - no code execution, no data modification, no denial of service. The primary limiting factor for defenders is the mandatory user-navigation step, making phishing or drive-by delivery the required delivery mechanism. |
| Impact | The CVSS base score of 4.3 accurately reflects a bounded privacy risk: limited cross-origin data leakage (C:L) with no integrity or availability impact. EPSS at 0.21% in the 11th percentile signals very low exploitation probability, consistent with the absence of a CISA KEV listing and no identified public POC. The AC:L and PR:N metrics indicate that if a user visits a malicious page, exploitation mechanics are straightforward - there is no complex exploit chain to execute - but the mandatory UI:R gate (victim must navigate to the attacker page) provides a meaningful real-world friction point. The Chromium team's own Medium classification aligns with the NVD score. This vulnerability is a genuine but lower-priority patching target: it poses a meaningful cross-site data privacy risk (e.g., leaking authenticated session content across origins) but carries no remote code execution or system integrity risk. Organizations running Chrome at scale should prioritize this patch as part of routine update cycles rather than emergency response. |
| Exploit ScenarioDerived | An attacker registers a convincing domain and hosts a crafted HTML page that invokes Chrome's Cast subsystem with maliciously structured input. When a victim using an unpatched Chrome version (below 151.0.7922.72) visits this page - delivered via phishing, malvertising, or a compromised site - the insufficient input validation in the Cast component allows the page to read data from a cross-origin context, potentially exposing authenticated content (e.g., tokens, user data) from another open tab or iframe. No public exploit code has been identified at time of analysis, so exploitation requires independent capability to develop the triggering HTML payload. |
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 Cast subsystem (all versions prior to 151.0.7922.72) enables a remote unauthenticated attacker to exfiltrate sensitive cross-origin data by luring a victim to a specially crafted HTML page. The vulnerability, rated Medium by the Chromium security team with a CVSS of 4.3, is bounded to a limited confidentiality impact with no code execution risk. No active exploitation is confirmed in CISA KEV, and EPSS at 0.21% (11th percentile) indicates a very low probability of widespread in-the-wild exploitation at time of analysis.
RemediationAI
Update Google Chrome to version 151.0.7922.72 or later; this is the vendor-released patch confirming the fix, as detailed in the stable channel advisory at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Chrome auto-updates by default for consumer installations, but enterprise administrators should verify deployment via fleet management tools (e.g., Google Admin Console, Intune, or endpoint management platforms) to confirm the patched version is applied across managed devices. As a targeted compensating control where immediate patching is not feasible, organizations can disable the Cast feature via the Chrome enterprise policy EnableMediaRouter set to false; this eliminates the Cast attack surface entirely but disables all Chromecast and Google Cast streaming functionality, which may impact productivity in environments that rely on screen casting. No other workarounds are identified that partially mitigate the vulnerability without removing Cast access.
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 vulnerability originates in Chrome's Cast component - the browser subsystem that powers Google Cast and Chromecast streaming functionality. CWE-20 (Improper Input Validation) identifies the root cause as insufficient sanitization of attacker-controlled input derived from a crafted HTML page before it is processed by the Cast subsystem, resulting in a same-origin policy bypass. The CPE identifier cpe:2.3:a:google:chrome applies broadly across Chrome desktop installations. The CVSS vector AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N confirms the flaw is network-reachable with low complexity, no privilege requirement, but requires user interaction (the victim navigating to the malicious page), and produces limited confidentiality impact with no effect on integrity or availability.
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 (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Network-delivered via crafted page (AV:N), victim must actively visit it (UI:R), no attacker privileges required (PR:N), impact is limited cross-origin data disclosure only (C:L, I:N, A:N).
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
4DescriptionCVE.org
Insufficient validation of untrusted input in Cast 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: 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.
Related Vulnerabilities in Google Chrome Multiple Security Flaws
View all 80Same weakness CWE-20 – Improper Input Validation
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-50722
GHSA-789q-pc44-64xf
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB