EUVD-2026-50790
GHSA-xr6x-3wm2-3g8p
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessExploit separate renderer RCE vulnerability
-
DeliveryAchieve renderer process compromise
-
ExploitDeliver crafted HTML page to victim
-
ExecutionLoader processes renderer input without sufficient validation
-
PersistBypass same-origin boundary
-
ImpactExfiltrate cross-origin 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 critical, non-negotiable prerequisite for exploitation is prior compromise of Chrome's renderer process - typically achieved via a separate, unpatched RCE vulnerability in Chrome's V8 JavaScript engine, Blink renderer, or media handling stack. Without renderer compromise, this vulnerability cannot be triggered regardless of attacker position or victim behavior. Beyond that, the victim must interact with attacker-controlled HTML content (UI:R), such as visiting a malicious web page or a legitimate page that has been injected with attacker content. No special target-side authentication, elevated privileges, or non-default Chrome configuration is required. Exploitation is strictly limited to confidentiality impact (cross-origin data exfiltration); it does not grant code execution or persistence on its own. All desktop platforms running Chrome prior to 151.0.7922.72 are in scope without platform-specific carve-outs. |
| Impact | The vendor-assigned CVSS 6.5 vector (AV:N/AC:L/PR:N/UI:R) materially understates attack complexity because AC:L does not capture the most significant prerequisite: the attacker must have already compromised Chrome's renderer process, typically via a separate and often critical-severity RCE vulnerability targeting the JavaScript engine or media parser. This positions CVE-2026-17664 as a second-stage vulnerability in a chained exploit rather than a standalone threat, and the true exploitability is substantially lower than AC:L implies. EPSS at 0.29% (21st percentile) reflects limited real-world exploitation activity, and the absence from CISA KEV corroborates no confirmed widespread exploitation at time of analysis. The C:H rating is well-grounded - successful exploitation enables exfiltration of cross-origin content such as authentication tokens, session cookies, or sensitive page data from other origins the victim is authenticated to. Integrity and availability are unaffected (I:N/A:N). Net assessment: meaningful risk only when paired with an active renderer exploit; standalone risk is low. |
| Exploit ScenarioDerived | An attacker who has separately leveraged a renderer RCE vulnerability to compromise Chrome's renderer process delivers a crafted HTML page to a victim already authenticated to sensitive internal applications. The compromised renderer exploits Loader's insufficient input validation to issue manipulated cross-origin resource requests, capturing responses - such as session tokens, CSRF nonces, or page content from banking or enterprise portals - that the same-origin policy would normally block. No public exploit code targeting CVE-2026-17664 specifically has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 31, 2026
Cross-origin data leak in Google Chrome's Loader component (all versions prior to 151.0.7922.72) enables an attacker who has already compromised the renderer process to exfiltrate sensitive data from other origins via a crafted HTML page. The flaw stems from insufficient input validation (CWE-20) in how Loader processes requests originating from a compromised renderer, bypassing same-origin protections. No public exploit code has been identified and EPSS sits at 0.29% (21st percentile), consistent with this vulnerability's role as a second-stage capability in a chained browser exploit rather than a standalone attack.
RemediationAI
Update Google Chrome to version 151.0.7922.72 or later immediately, as documented in the Chrome stable channel advisory at http://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Chrome auto-updates by default on most consumer installations; enterprise administrators should verify deployment via Chrome Browser Cloud Management or group policy and confirm the build version is at or above 151.0.7922.72. No vendor-documented workarounds exist for this specific flaw. As a compensating control where immediate patching is blocked, consider restricting browser access to sensitive internal web applications or enforcing network-layer controls (e.g., allowlisting only trusted origins for authenticated sessions) to reduce the cross-origin data exfiltration surface - these do not remediate the flaw but raise the bar for meaningful data theft if renderer compromise occurs.
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 Loader component in Chrome's browser process is responsible for fetching, routing, and dispatching web resources on behalf of renderer processes. Even after a renderer is compromised, the sandbox boundary should prevent direct cross-origin data access - but insufficient validation of renderer-supplied inputs in Loader allows a malicious renderer to manipulate resource requests or responses such that cross-origin data is returned to attacker-controlled context. CWE-20 (Improper Input Validation) identifies the root cause as a failure to adequately verify the integrity or trustworthiness of inputs arriving from the already-compromised renderer before acting on them at the browser-process level. The affected CPE (cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) covers all Chrome releases on all platforms prior to 151.0.7922.72, as confirmed by the EUVD-2026-50790 entry and the Chrome stable channel advisory.
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:H/I:N/A:N
Renderer process compromise prerequisite elevates AC to H; no target-system privileges needed; user page visit required; impact is confidentiality only.
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 Loader in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
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