CVE-2026-16424: Use after free in GPU in Google Chrome on Android prior to 150.0.7871.182 allowed a remote attacker who had co

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

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

Q: Is CVE-2026-16424 being exploited?

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

CVE-2026-16424 affects chrome. Severity is critical (CVSS 9.6). Use after free in GPU in Google Chrome on Android prior to 150.0.7871.182 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

Q: How urgent is CVE-2026-16424?

Priority 40/100. Critical severity

This month

CRITICAL 9.6UPGRADE

CVE-2026-16424 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 GPU in Google Chrome on Android prior to 150.0.7871.182 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

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 73%)
CISA exploited list	No
Weakness	CWE-416
Published	2026-07-21
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-21 23:17 UTCPublished CVE record published
2026-10-24 17:10 UTCUpdated Record last modified

google chrome UPGRADE

Affected: < 150.0.7871.182

Fixed in: 150.0.7871.182

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 150.0.7871.182 (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 · newscache · FIXED · 1.3.22-1.fc46 · FEDORA-2026-49b088f8ca · source

sudo dnf upgrade --advisory=FEDORA-2026-49b088f8ca

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 · 150.0.7871.181-1~deb12u1

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

Debian 13 · chromium · FIXED · 150.0.7871.181-1~deb13u1

sudo apt update && sudo apt install --only-upgrade chromium dpkg --compare-versions "$(dpkg-query -W -f='${Version}' chromium)" ge "150.0.7871.181-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-16424?

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

Is CVE-2026-16424 being exploited?

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

CVE-2026-16424 affects chrome. Severity is critical (CVSS 9.6). Use after free in GPU in Google Chrome on Android prior to 150.0.7871.182 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

How urgent is CVE-2026-16424?

Priority 40/100. Critical severity

Software pages

Android 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-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
CVE-2026-16422 HIGH 7.5 UPGRADE Insufficient validation of untrusted input in Certificate in Google Chrome on Linux prior to 150.0.7871.182 al

References

← Back to latest CVEs