Security readout for executives and security teams
Plain-English summary
A malicious webpage could potentially let an attacker break out of Chrome’s security sandbox on an iPhone or iPad. Successful exploitation requires a user to open the crafted page, but could compromise data, modify the device’s browser context, or disrupt availability. The supplied CVSS score is 9.6.
Executive priority
Treat this as an urgent mobile-browser update because the supplied severity is critical and potential impact spans data confidentiality, integrity, and availability. Prioritize rapid inventory and remediation, while recognizing that the provided sources do not confirm exploitation in the wild.
Technical view
CVE-2026-17669 is an inappropriate implementation weakness, categorized as CWE-693, in Chrome for iOS before 151.0.7922.72. A remote, unauthenticated attacker could potentially trigger a sandbox escape through crafted HTML. The supplied vector indicates low complexity, required user interaction, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to Chrome for iOS installations older than 151.0.7922.72, according to the description. Organizations with unmanaged iPhones or iPads, delayed mobile application updates, or incomplete browser inventories are more likely to retain vulnerable installations. No CPE identifiers were supplied.
Exploitation context
The source bundle does not establish active exploitation, and the CVE is not identified as being in KEV. Exploitation requires user interaction with crafted HTML. Public exploit availability, attack-chain prerequisites, and reliability are not documented in the supplied evidence.
Researcher notes
The bundle contains an inconsistency: the description says versions before 151.0.7922.72 are affected, while the affected-version entry lists 151.0.7922.72. Additionally, the referenced release title identifies a desktop update despite the CVE describing Chrome for iOS. Confirm authoritative vendor details before final scoping.
Mitigation direction
- Update Chrome for iOS to version 151.0.7922.72 or later.
- Use mobile-device management to enforce application updates where available.
- Prioritize devices used for privileged administration or sensitive business data.
- Check Google and Chromium guidance for any additional mitigations or revised version information.
Validation and detection
- Inventory Chrome versions across managed iPhones and iPads.
- Confirm every installation reports version 151.0.7922.72 or later.
- Review mobile-management reports for devices failing or deferring application updates.
- Monitor vendor advisories for exploitation-status or remediation changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-693: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-17669 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.htmlCVE reference, Chrome
- https://issues.chromium.org/issues/513142464CVE reference, Chrome
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Protection Mechanism Failure
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.