Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Referrer leakage is a confidentiality impact (C:L), not integrity; no integrity or availability impact applies to policy bypass of this class.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Insufficient policy enforcement in Chrome for iOS in Google Chrome on iOS prior to 150.0.7871.47 allowed a remote attacker to bypass no-referrer policy via a crafted HTML page. (Chromium security severity: Low)
AnalysisAI
No-referrer policy bypass in Google Chrome for iOS prior to 150.0.7871.47 allows a remote attacker to capture referrer URL information that the browser was supposed to suppress. Exploitation requires user interaction - the victim must visit a crafted HTML page served by the attacker - and exploits a client-side enforcement gap (CWE-602) specific to the iOS build of Chrome. EPSS is 0.19% (9th percentile) and no active exploitation or KEV listing exists, consistent with the Low Chromium severity rating.
Technical ContextAI
CWE-602 (Client-Side Enforcement of Server-Side Security) identifies cases where the browser, rather than the server, is expected to enforce a security policy but fails to do so. The Referrer-Policy HTTP header - specifically the 'no-referrer' directive - instructs browsers to omit the Referer header on navigations originating from a page, protecting sensitive URL parameters or navigation history from leaking to third parties. Chrome's iOS implementation diverges from the intended behavior when processing certain crafted HTML constructs, causing it to emit the Referer header despite the policy. The affected CPE scope is Google Chrome on iOS, versions prior to 150.0.7871.47, meaning other Chrome platforms (Android, Desktop) are not implicated by this specific issue.
RemediationAI
Update Google Chrome on iOS to version 150.0.7871.47 or later via the Apple App Store. The patch is confirmed available from the vendor per the Chrome Releases blog at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. For environments where immediate update is not possible, a compensating control is to use an alternative iOS browser (Safari, Firefox for iOS) for sessions where referrer-policy suppression is security-critical, understanding this shifts browser attack surface. Web application operators who rely on no-referrer policy for sensitive URL parameter protection should consider server-side validation to not expose sensitive data in URLs at all, as defense-in-depth against client enforcement gaps of this class.
Same technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-40762
GHSA-mhhg-7472-3pg7