Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconCraft malicious HTML page targeting Chrome iOS policy
-
DeliveryHost on attacker-controlled server
-
ExploitDeliver phishing link to iOS Chrome user
-
InstallVictim opens page in unpatched Chrome for iOS
-
C2Policy enforcement bypass triggered
-
ExecuteDiscretionary access controls circumvented
-
ImpactUnauthorized integrity impact achieved
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to be running Google Chrome for iOS on an Apple iOS device with a Chrome version below 151.0.7922.72. The attacker must deliver a crafted HTML page and the victim must actively open it in Chrome for iOS (UI:R per CVSS - passive or drive-by exploitation without any user interaction is not possible). No attacker authentication or privileges are required (PR:N). The vulnerability is scoped exclusively to the iOS build of Chrome; users on desktop Chrome, Chrome for Android, or Safari are not affected by this specific flaw. The non-automatable SSVC classification further indicates that bulk, scripted exploitation across large populations is not feasible, limiting realistic risk to more targeted delivery scenarios. |
| Impact | The CVSS 6.5 score with vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N indicates a medium-severity vulnerability: network reachable, low complexity, no attacker privileges, but requiring user interaction, with high integrity impact limited to the browser's scope. EPSS at 0.18% (8th percentile) signals very low current exploitation probability, consistent with SSVC's exploitation classification of none and automatable classification of no. SSVC technical impact is partial, aligning with the bounded scope (S:U) and absence of confidentiality or availability impact. No KEV listing exists and no public exploit code has been identified. The vulnerability is iOS-platform-specific, further constraining the exploitable population to Chrome for iOS users running versions below 151.0.7922.72. Combined, these signals indicate this is a real but lower-priority issue: a patch should be applied, but there is no evidence of active exploitation or weaponized tooling that would warrant emergency response. |
| Exploit ScenarioDerived | An attacker registers or compromises a website and serves a specially crafted HTML page designed to trigger Chrome for iOS's insufficient policy enforcement. The attacker then distributes a link to that page via phishing email, SMS, or social media to target iOS Chrome users; once a victim opens the link in Chrome for iOS on an unpatched device, the crafted page circumvents discretionary access controls, allowing the attacker to achieve unauthorized integrity impacts within the browser's content context. No public exploit code is currently known, limiting this scenario primarily to motivated, targeted actors rather than commodity exploitation. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 30, 2026
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.
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.
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
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.
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: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
3DescriptionCVE.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)
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Related Vulnerabilities in Google Chrome 151 Security Vulnerabilities
View all 80Same 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 |
EUVD-2026-50666
GHSA-8hh5-hmcm-cgrx
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB