CVE-2026-17832: Use after free in ANGLE in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised

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

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

Q: Is CVE-2026-17832 being exploited?

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

CVE-2026-17832 affects chrome. Severity is critical (CVSS 9.6). Use after free in ANGLE 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)

Q: How urgent is CVE-2026-17832?

Priority 40/100. Critical severity

This month

CRITICAL 9.6UPGRADE

CVE-2026-17832 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.

Use after free in ANGLE 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 score	9.6 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 74%)
CISA exploited list	No
Weakness	CWE-416
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 23: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.

Exact fixes by distribution

Fedora 46 · kwin-zones · FIXED · 1.0.13-1.fc46 · FEDORA-2026-95888f332b · source

sudo dnf upgrade --advisory=FEDORA-2026-95888f332b

Fedora ELN · nginx-mod-brotli · FIXED · 1.0.0~rc-16.eln159 · FEDORA-2026-501a6a8273 · source

sudo dnf upgrade --advisory=FEDORA-2026-501a6a8273

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

Debian 12 · webkit2gtk · NO FIX YET

Debian 13 · webkit2gtk · FIXED · 2.54.0-1~deb13u1

sudo apt update && sudo apt install --only-upgrade webkit2gtk dpkg --compare-versions "$(dpkg-query -W -f='${Version}' webkit2gtk)" ge "2.54.0-1~deb13u1" && echo PATCHED || echo STILL-VULNERABLE

RHEL 8 · webkit2gtk3 · FIXED · webkit2gtk3-2.54.0-1.el8_10

sudo dnf upgrade --advisory=RHSA-2026:74084 rpm -q webkit2gtk3

RHEL 9 · webkit2gtk3 · FIXED · webkit2gtk3-2.54.0-1.el9_8

sudo dnf upgrade --advisory=RHSA-2026:69098 rpm -q webkit2gtk3

RHEL 10 · firefox · NOT AFFECTED

RHEL 10 · thunderbird · NOT AFFECTED

RHEL 6 · webkitgtk · DEFERRED

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

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

Is CVE-2026-17832 being exploited?

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

CVE-2026-17832 affects chrome. Severity is critical (CVSS 9.6). Use after free in ANGLE 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)

How urgent is CVE-2026-17832?

Priority 40/100. Critical severity

Software pages

Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-17655 CRITICAL 9.6 UPGRADE Insufficient validation of untrusted input in ANGLE in Google Chrome prior to 151.0.7922.72 allowed a remote a
CVE-2026-17687 CRITICAL 9.6 UPGRADE Type Confusion in ANGLE in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised
CVE-2026-17697 CRITICAL 9.6 UPGRADE Type Confusion in ANGLE in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to potentially perfo
CVE-2026-17671 CRITICAL 9.6 UPGRADE Insufficient validation of untrusted input in ANGLE in Google Chrome prior to 151.0.7922.72 allowed a remote a
CVE-2026-17676 CRITICAL 9.6 UPGRADE Inappropriate implementation in ANGLE in Google Chrome on Android prior to 151.0.7922.72 allowed a remote atta

References

← Back to latest CVEs