Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-17837: Insufficient validation of untrusted input in DevTools in Google Chrome prior to 151.0.7922.72 allowed a remot

40
This month
CRITICAL 9.6UPGRADE

CVE-2026-17837 is a critical-severity flaw (CVSS 9.6) 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 DevTools in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)

Why this priority

  • Critical severity

A fixed release or distro patch exists.

Risk facts

CVSS score9.6 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance0.3% (top 73%)
CISA exploited listNo
WeaknessCWE-20
Published2026-07-30
Last modified2026-10-23
Publisher (CNA): Chrome · Vendor: google

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 ELN · ntpd-rs · FIXED · 1.7.2-3.eln159 · FEDORA-2026-57e4a99310 · source
sudo dnf upgrade --advisory=FEDORA-2026-57e4a99310
Fedora 46 · moby-engine · FIXED · 29.9.2-2.fc46 · FEDORA-2026-4856be87b3 · source
sudo dnf upgrade --advisory=FEDORA-2026-4856be87b3
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

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

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-17837?

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

Is CVE-2026-17837 being exploited?

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

CVE-2026-17837 affects chrome. Severity is critical (CVSS 9.6). Insufficient validation of untrusted input in DevTools in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium sec

How urgent is CVE-2026-17837?

Priority 40/100. Critical severity

Related CVEs

References

← Back to latest CVEs