CVE-2026-16413: Out of bounds write in ANGLE in Google Chrome prior to 150.0.7871.182 allowed a remote attacker who had compro

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

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

Q: Is CVE-2026-16413 being exploited?

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

CVE-2026-16413 affects chrome. Severity is high (CVSS 8.3). Out of bounds write in ANGLE in Google Chrome 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)

Routine

HIGH 8.3UPGRADE

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

Out of bounds write in ANGLE in Google Chrome 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

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.3 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 82%)
CISA exploited list	No
Weakness	CWE-787
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:16 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

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

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

Is CVE-2026-16413 being exploited?

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

CVE-2026-16413 affects chrome. Severity is high (CVSS 8.3). Out of bounds write in ANGLE in Google Chrome 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-16413?

Priority 34/100. High severity

Software pages

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-16424 CRITICAL 9.6 UPGRADE Use after free in GPU in Google Chrome on Android prior to 150.0.7871.182 allowed a remote attacker who had co
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

References

← Back to latest CVEs