Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-17930: Insufficient validation of untrusted input in Extensions in Google Chrome prior to 151.0.7922.72 allowed a rem

32
Routine
HIGH 7.5UPGRADE

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

Insufficient validation of untrusted input in Extensions in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to perform privilege escalation via a crafted HTML page. (Chromium security severity: Low)

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionRequired
EPSS exploit chance0.3% (top 76%)
CISA exploited listNo
WeaknessCWE-20
Published2026-07-30
Last modified2026-10-23
Publisher (CNA): Chrome · Vendor: google

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

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.

Exact fixes by distribution

Fedora 46 · sugar-clock · FIXED · 22.1-17.fc46 · FEDORA-2026-57948849df · source
sudo dnf upgrade --advisory=FEDORA-2026-57948849df
Fedora ELN · selinux-policy · FIXED · 45.23-1.eln159 · FEDORA-2026-3668c969a2 · source
sudo dnf upgrade --advisory=FEDORA-2026-3668c969a2
Ubuntu 22.04 · chromium-browser · NOT AFFECTED
Ubuntu 24.04 · chromium-browser · NOT AFFECTED
Debian 12 · chromium · FIXED · 151.0.7922.71-1~deb12u1
sudo apt update && sudo apt install --only-upgrade chromium dpkg --compare-versions "$(dpkg-query -W -f='${Version}' chromium)" ge "151.0.7922.71-1~deb12u1" && echo PATCHED || echo STILL-VULNERABLE
Debian 13 · chromium · FIXED · 151.0.7922.71-1~deb13u1
sudo apt update && sudo apt install --only-upgrade chromium dpkg --compare-versions "$(dpkg-query -W -f='${Version}' chromium)" ge "151.0.7922.71-1~deb13u1" && echo PATCHED || echo STILL-VULNERABLE
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-17930?

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

Is CVE-2026-17930 being exploited?

CVE-2026-17930 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-17930 affect?

CVE-2026-17930 affects chrome. Severity is high (CVSS 7.5). Insufficient validation of untrusted input in Extensions in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to perform privilege escalation via a crafted HTML page. (Chromium security

How urgent is CVE-2026-17930?

Priority 32/100. High severity

Software pages

Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.