VulnerabilityPublished 30 Jul 2026

CVE-2026-17703: Google Chrome · Policy Bypass

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 151.0.7922.72 when convenient.

Data as of 28 Oct 2026, 05:11 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 151.0.7922.72

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Google Chrome to 151.0.7922.72.

Affected software

Product	Affected	Fixed in
GoogleChrome	Affected >=151.0.7922.72 <151.0.7922.72	Fixed in 151.0.7922.72

AI-suggested

The provided vendor advisory link should be monitored for updates on official fixes or mitigations. Until a patch is confirmed, users should exercise caution when navigating untrusted web content on affected Chrome for iOS versions.

Description

CVE-2026-17703 is a policy bypass vulnerability in Google Chrome for iOS versions prior to 151.0.7922.72. It allows a remote attacker to bypass navigation restrictions by using a crafted HTML page. The vulnerability is classified with a medium severity and has a CVSS score of 6.5. No known exploits are reported in the wild. The vendor advisory link is provided but does not explicitly confirm patch availability or remediation status.

Impact

An attacker can bypass navigation restrictions in affected versions of Chrome for iOS, potentially leading to unauthorized navigation actions that could compromise the integrity of user sessions or browser state. There is no impact on confidentiality or availability reported. No active exploitation in the wild has been observed.

Summary

This vulnerability involves insufficient policy enforcement in Google Chrome on iOS before version 151.0.7922.72. A remote attacker can exploit this flaw by crafting a malicious HTML page that bypasses navigation restrictions intended to control or limit user navigation within the browser. The issue is tracked as CWE-602 (Improper Restriction of Navigation). The CVSS vector indicates the attack requires no privileges, has low attack complexity, requires user interaction, and impacts integrity without affecting confidentiality or availability.

CWE-602Client-Side Enforcement of Server-Side Security (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely.
Architecture and Design
If some degree of trust is required between the two entities, then use integrity checking and strong authentication to ensure that the inputs are coming from a trusted source.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.1 (opens in a new tab)
V1.5.3 (opens in a new tab)
V4.1.1 (opens in a new tab)
Attack patterns
Manipulating Hidden Fields (opens in a new tab)
Create Malicious Client (opens in a new tab)
Removing Important Client Functionality (opens in a new tab)
Removing/short-circuiting 'Purse' logic: removing/mutating 'cash' decrements (opens in a new tab)
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Aug 2026, 17:35 UTC

WeaknessesCWE-602

Technical details

References

Community reviews

Related threats