EUVD-2026-50619
GHSA-9j3q-3r6g-76c2
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent network position (LAN/Wi-Fi)
-
DeliveryCraft malicious Cast protocol traffic
-
ExploitSend traffic to victim's Chrome
-
ExecutionTrigger insufficient Cast input validation
-
ImpactLeak cross-origin browser data to attacker
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | The attacker must be on the same local network segment (LAN or Wi-Fi) as the targeted Chrome user - remote Internet-based exploitation is not possible. The Cast feature must be active or reachable in Chrome (enabled by default in standard Chrome installations). No authentication to Chrome or the target web application is required. Exploitation is limited by the requirement for physical or logical network adjacency; a threat actor on the open Internet cannot directly reach the victim. The impact is further bounded to confidentiality only - no code execution or integrity modification is possible via this flaw. The non-automatable SSVC classification suggests that crafting effective malicious Cast traffic likely requires per-target adaptation rather than a generic spray-and-pray approach. |
| Impact | Real-world risk is low-to-moderate. The CVSS 4.3 score reflects a limited-scope information disclosure with an adjacent network vector, meaning remote Internet-based exploitation is not possible - the attacker must be on the same LAN or Wi-Fi segment. EPSS stands at just 0.12% (2nd percentile), indicating extremely low observed exploitation probability across the broader threat landscape. CISA SSVC classifies exploitation status as 'none' and the technical impact as 'partial', and automatable as 'no', reinforcing that this is not a trivially weaponizable flaw. There is no CISA KEV listing and no confirmed public POC. The combination of physical network proximity requirement, low EPSS, no KEV, no POC, and partial confidentiality-only impact places this well below typical emergency-patch thresholds. However, in corporate, hospitality, or shared Wi-Fi environments where untrusted peers share the same network, the risk is more relevant, particularly where Cast is actively used. The missing detail of exactly which cross-origin data can be leaked (cookies, tokens, page content) prevents a more precise impact determination. |
| Exploit ScenarioDerived | An attacker connected to the same Wi-Fi network as a target user sends specially crafted Cast protocol messages to the victim's Chrome browser. The insufficient input validation in the Cast component causes Chrome to process the malicious traffic in a way that exposes data from a cross-origin context - for example, content or tokens from an already-open web page - back to the attacker. No user interaction or credentials are required beyond network adjacency. |
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 component allows an unauthenticated attacker positioned on the same local network segment to read data from origins they should not have access to via maliciously crafted network traffic. All Chrome versions prior to 151.0.7922.72 are affected. No public exploit code exists and CISA has not listed this in the KEV catalog, placing real-world risk at low-to-moderate despite the unauthenticated attack vector.
RemediationAI
Update Google Chrome to version 151.0.7922.72 or later, which contains the vendor-released fix per the Stable Channel Update advisory at http://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Chrome typically updates automatically, but administrators in managed enterprise environments should push this update via policy. As a compensating control where immediate patching is not feasible, disabling or restricting use of the Cast feature via Chrome enterprise policy (CastEnabled=false) eliminates the attack surface entirely, though this removes the ability to cast to Chromecast and compatible devices. Restricting untrusted devices on shared network segments (e.g., client isolation on Wi-Fi, network segmentation) reduces attacker adjacency opportunity but does not address the underlying flaw.
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 Cast component in Google Chrome implements the Google Cast protocol, enabling Chrome to stream content to Chromecast and compatible devices over the local network. CWE-20 (Improper Input Validation) indicates that the Cast subsystem fails to adequately sanitize or validate input received from network peers, allowing an attacker-controlled source to inject or manipulate Cast protocol messages. Because Cast inherently operates across the adjacent network boundary (AV:A per CVSS), an attacker must be co-located on the same LAN or WLAN segment. The insufficient validation allows the attacker's malicious traffic to cause the browser to expose data belonging to a different web origin, violating the Same-Origin Policy guarantees users depend on for cross-site isolation. Affected product identified via CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*.
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:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Adjacent vector reflects LAN-only reachability; PR:N confirmed by CVSS input; C:L reflects partial cross-origin data disclosure with no integrity or availability impact.
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
Insufficient validation of untrusted input in Cast in Google Chrome prior to 151.0.7922.72 allowed an attacker on the local network segment to leak cross-origin data via malicious network traffic. (Chromium security severity: Medium)
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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 Prior to 151.0.7922.72 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 |
Exploit-DB