Quick answers
- Is CVE-2026-17917 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-17917 being exploited in the wild.
- How severe is CVE-2026-17917?
- Informational severity, with a CVSS score of 0, published 30 July 2026.
- Which products and versions are affected?
- Google Chrome for iOS prior to 151.0.7922.72.
- Is there a fix for CVE-2026-17917?
- A patch was published on 2026-07-29: Stable Channel Update for Desktop/iOS released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-17917 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-17917?
- Check whether you run Google Chrome for iOS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability classified as insufficient policy enforcement exists in the Chrome for iOS component of Google Chrome. The flaw resides in how the browser handles discretionary access control (DAC) when processing web content. A remote, unauthenticated attacker can exploit this by enticing a user to visit a maliciously crafted HTML page. Successful exploitation allows the attacker to bypass intended access restrictions. The issue is resolved in version 151.0.7922.72 and later.
Affected products
- Google Chrome for iOS prior to 151.0.7922.72
Timeline
- 2026-07-29: patched: Stable Channel Update for Desktop/iOS released
- 2026-07-30: disclosed: NVD publication date