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

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

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

Q: Is CVE-2026-17729 being exploited?

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

CVE-2026-17729 affects chrome. Severity is high (CVSS 8.8). Use after free in V8 in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity: Medium)

Routine

HIGH 8.8UPGRADE

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

Use after free in V8 in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity: Medium)

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.4% (top 70%)
CISA exploited list	No
Weakness	CWE-416
Published	2026-07-30
Last modified	2026-10-24

Publisher (CNA): Chrome · Vendor: google

Last updated 2026-10-24 · 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-24 13: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 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.

Write-up: issues.chromium.org/issues/520656237

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

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

Is CVE-2026-17729 being exploited?

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

CVE-2026-17729 affects chrome. Severity is high (CVSS 8.8). Use after free in V8 in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity: Medium)

How urgent is CVE-2026-17729?

Priority 38/100. High severity

Software pages

Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-15764 HIGH 7.5 UPGRADE Use after free in Ozone in Google Chrome on Linux prior to 150.0.7871.125 allowed a remote attacker who convin
CVE-2026-15776 HIGH 8.8 UPGRADE Inappropriate implementation in V8 in Google Chrome prior to 150.0.7871.125 allowed a remote attacker to execu
CVE-2026-15773 CRITICAL 9.6 UPGRADE Use after free in Core in Google Chrome on Windows prior to 150.0.7871.125 allowed a remote attacker to potent
CVE-2026-15767 HIGH 8.8 UPGRADE Heap buffer overflow in libyuv in Google Chrome on Windows prior to 150.0.7871.125 allowed a remote attacker t
CVE-2026-15769 HIGH 8.3 UPGRADE Insufficient validation of untrusted input in Linux Toolkit Theming in Google Chrome on Linux prior to 150.0.7

References

← Back to latest CVEs