Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Network-delivered crafted HTML requires victim to open the page (UI:R); no attacker privileges needed; integrity-only impact within browser scope with no confidentiality or availability effect.
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 policy enforcement in Chrome for iOS in Google Chrome on iOS prior to 151.0.7922.72 allowed a remote attacker to bypass discretionary access control via a crafted HTML page. (Chromium security severity: Low)
AnalysisAI
Insufficient policy enforcement in Google Chrome for iOS prior to version 151.0.7922.72 enables a remote attacker to bypass discretionary access controls (CWE-284) by delivering a crafted HTML page to a victim, resulting in high integrity impact with no confidentiality or availability consequence. The CVSS vector (AV:N/AC:L/PR:N/UI:R) confirms network reachability with no attacker privileges needed, though user interaction is required. With EPSS at 0.18% (8th percentile), SSVC exploitation classified as none, and no public exploit identified at time of analysis, real-world mass exploitation risk is low despite the meaningful integrity bypass potential on a widely-used mobile browser.
Technical ContextAI
Chrome for iOS operates under Apple platform restrictions that mandate WebKit as the rendering engine rather than Blink, meaning iOS-specific code paths diverge substantially from desktop Chromium's policy enforcement stack. CWE-284 (Improper Access Control) identifies the root cause as a failure to correctly enforce discretionary access control policies for web content, allowing a crafted HTML page to access or modify resources beyond its permitted scope. The CPE identifier cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* covers the Chrome application, and the EUVD (EUVD-2026-50666) confirms the version boundary at 151.0.7922.72. The iOS-specific build introduces unique policy enforcement code separate from desktop Chrome, which is a historically fertile area for platform-specific bypass vulnerabilities. Chromium issue 511816897 references the underlying tracker for additional technical specifics, though full details were not available in provided data.
RemediationAI
The primary fix is to upgrade Google Chrome for iOS to version 151.0.7922.72 or later, delivered via the Apple App Store. The vendor release advisory documenting this fix is available at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. No documented workarounds specific to this vulnerability exist; as a compensating control prior to patching, users should avoid visiting untrusted or unfamiliar websites in Chrome for iOS and exercise caution with links received via email or messaging, given the UI:R (user interaction required) attack vector. Enabling automatic app updates on iOS ensures the patch is delivered without manual action and reduces the window of exposure on managed and consumer devices alike.
Same weakness CWE-284 – Improper Access Control
View allSame technique Authentication Bypass
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 |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-50666
GHSA-8hh5-hmcm-cgrx