CVE-2026-17917: Insufficient policy enforcement in Chrome for iOS in Google Chrome on iOS prior to 151.0.7922.72 allowed a rem

Q: How do I fix CVE-2026-17917?

chrome: upgrade to 151.0.7922.72. Exact commands for each OS are on this page.

Q: Is CVE-2026-17917 being exploited?

CVE-2026-17917 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-17917 affect?

CVE-2026-17917 affects chrome. Severity is medium (CVSS 6.5). 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)

Q: How urgent is CVE-2026-17917?

Priority 28/100. No elevated risk signals yet.

Routine

MEDIUM 6.5UPGRADE

CVE-2026-17917 is a medium-severity flaw (CVSS 6.5) affecting chrome. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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)

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 80%)
CISA exploited list	No
Weakness	CWE-284
Published	2026-07-30
Last modified	2026-10-23

Publisher (CNA): Chrome · Vendor: google

Last updated 2026-10-23 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-07-30 01:16 UTCPublished CVE record published
2026-10-23 22:10 UTCUpdated Record last modified

google chrome UPGRADE

Affected: < 151.0.7922.72

Fixed in: 151.0.7922.72

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy chrome || rpm -q chrome || chrome --version

2. UPGRADE to 151.0.7922.72 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade chrome

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade chrome

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-17917?

chrome: upgrade to 151.0.7922.72. Exact commands for each OS are on this page.

Is CVE-2026-17917 being exploited?

CVE-2026-17917 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-17917 affect?

CVE-2026-17917 affects chrome. Severity is medium (CVSS 6.5). 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)

How urgent is CVE-2026-17917?

Priority 28/100. No elevated risk signals yet.

Software pages

iOS vulnerabilities · Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-16420 HIGH 8.8 UPGRADE Type Confusion in WebAudio in Google Chrome prior to 150.0.7871.182 allowed a remote attacker to execute arbit
CVE-2026-16421 HIGH 8.8 UPGRADE Inappropriate implementation in WebAudio in Google Chrome prior to 150.0.7871.182 allowed a remote attacker to
CVE-2026-16418 HIGH 8.8 UPGRADE Stack buffer overflow in V8 in Google Chrome prior to 150.0.7871.182 allowed a remote attacker to execute arbi
CVE-2026-16424 CRITICAL 9.6 UPGRADE Use after free in GPU in Google Chrome on Android prior to 150.0.7871.182 allowed a remote attacker who had co
CVE-2026-16419 CRITICAL 9.6 UPGRADE Out of bounds read and write in ANGLE in Google Chrome on Android prior to 150.0.7871.182 allowed a remote att

References

← Back to latest CVEs