Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker crafts malicious HTML page
-
DeliveryVictim clicks link in Chrome for iOS
-
ExploitPage loads and triggers origin validation bypass
-
ExecutionAttacker's script reads cross-origin data
-
ImpactStolen data exfiltrated to attacker server
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Origin validation
|
| Exploitation Conditions | Exploitation requires the victim to be running Google Chrome on an iOS device (iPhone or iPad) at any version prior to 151.0.7922.72 - desktop Chrome and all other iOS browsers including Safari are not affected. User interaction is mandatory: the victim must actively navigate to or load a crafted HTML page, such as via a phishing link or malicious advertisement. The CVSS vector (PR:N) confirms no authentication to any service is required on the attacker's side. The cross-origin data leakage is bounded to what the browser can observe in the affected code path, limiting impact to partial confidentiality loss (C:L). Exploitation is further constrained to iOS-platform deployments of Chrome, significantly narrowing the exposed population compared to vulnerabilities affecting all Chrome platforms. Non-default configurations are not required - any iOS Chrome user below the fix version browsing the web is potentially exposed. |
| Impact | The CVSS 3.1 score of 4.3 (Medium) with vector AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N accurately reflects a moderate but limited threat profile: exploitable over the network with low complexity, no required privileges, but constrained by mandatory user interaction and limited to partial confidentiality loss with no integrity or availability impact. EPSS at 0.21% (11th percentile) is consistent with a platform-scoped, medium-severity information disclosure with no public exploit tooling - exploitation is possible but not a near-term commodity risk. The absence of a KEV listing further supports this as a non-actively-exploited vulnerability. The practical risk ceiling is bounded by the iOS-only scope (desktop Chrome users and non-Chrome iOS browser users are unaffected) and the C:L impact rating, which implies partial rather than wholesale data exfiltration. This is a genuine security flaw warranting prompt patching, but does not represent an emergency priority absent additional threat intelligence. |
| Exploit ScenarioDerived | An attacker crafts a malicious HTML page hosting JavaScript that exploits Chrome for iOS's origin validation flaw and distributes it via phishing email or malicious advertisement. When an iOS user clicks the link and the page loads in an unpatched Chrome browser, the attacker's page reads data from a cross-origin context - for example, content or session artifacts from a site the victim is concurrently authenticated to - and transmits it to an attacker-controlled server. No public POC is available, but the attack requires only a single click from the victim, making social engineering the primary delivery mechanism. |
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 for iOS prior to 151.0.7922.72 exposes sensitive information from other browser origins when a user visits a specially crafted HTML page. The root cause is an inappropriate implementation of origin validation (CWE-346) within Chrome's iOS-specific code path, breaking the browser's same-origin policy boundary. No public exploit code or active exploitation has been identified; EPSS probability stands at 0.21% (11th percentile), and the vulnerability is absent from the CISA KEV catalog, indicating low near-term exploitation pressure.
RemediationAI
Update Google Chrome on iOS to version 151.0.7922.72 or later via the Apple App Store; this is the only confirmed fix per the vendor advisory at http://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. If an immediate App Store update is not feasible in managed iOS environments, organizations can instruct users to use Safari or another WebKit-based browser as a temporary alternative, which avoids the vulnerable Chrome-specific implementation - note this may affect enterprise app compatibility or browser policy compliance. No server-side compensating controls exist for this client-side browser flaw, as the vulnerability resides entirely within the Chrome iOS application. Enforcing mobile device management (MDM) policies that restrict browsing to updated browser versions is advisable for security-sensitive environments.
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
CWE-346 (Origin Validation Error) describes failures to properly verify that data or messages originate from the expected source, which in browser contexts directly undermines the Same-Origin Policy (SOP) - the foundational isolation mechanism separating web origins. Chrome on iOS operates under constraints distinct from desktop Chrome because Apple mandates use of the WebKit rendering engine on iOS, meaning Chrome for iOS uses a platform-specific implementation layer that diverges from Chromium's standard Blink engine. This divergence creates iOS-unique code paths where origin-boundary enforcement may be implemented differently, introducing surface area for subtle logic errors. The affected CPE (cpe:2.3:a:google:chrome) scoped to the iOS platform corroborates that this flaw is confined to the iOS implementation rather than shared Chromium code. The consequence is that attacker-controlled page content can read data belonging to a different origin than intended.
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 delivery via crafted page, no privileges needed, user must visit page (UI:R), limited cross-origin read only (C:L), 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
4DescriptionCVE.org
Inappropriate implementation in Chrome for iOS in Google Chrome on iOS 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-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-50711
GHSA-4h42-5qrh-hrmp
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB