CVE-2026-19137: Use after free in WebGL in Google Chrome on Android prior to 151.0.7922.109 allowed a remote attacker who had

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

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

Q: Is CVE-2026-19137 being exploited?

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

CVE-2026-19137 affects chrome. Severity is high (CVSS 8.3). Use after free in WebGL in Google Chrome on Android prior to 151.0.7922.109 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Cri

Routine

HIGH 8.3UPGRADE

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

Use after free in WebGL in Google Chrome on Android prior to 151.0.7922.109 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

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 78%)
CISA exploited list	No
Weakness	CWE-416
Published	2026-08-06
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-08-06 22:16 UTCPublished CVE record published
2026-10-23 21:10 UTCUpdated Record last modified

google chrome UPGRADE

Affected: < 151.0.7922.109

Fixed in: 151.0.7922.109

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.109 (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 · selinux-policy · FIXED · 45.23-1.eln159 · FEDORA-2026-3668c969a2 · source

sudo dnf upgrade --advisory=FEDORA-2026-3668c969a2

Fedora 46 · sugar-toolkit-gtk3 · FIXED · 0.122-2.fc46 · FEDORA-2026-d11eb2faf0 · source

sudo dnf upgrade --advisory=FEDORA-2026-d11eb2faf0

Ubuntu 22.04 · chromium-browser · NOT AFFECTED

Ubuntu 24.04 · chromium-browser · NOT AFFECTED

Debian 12 · chromium · FIXED · 151.0.7922.108-1~deb12u1

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

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

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

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

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

Is CVE-2026-19137 being exploited?

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

CVE-2026-19137 affects chrome. Severity is high (CVSS 8.3). Use after free in WebGL in Google Chrome on Android prior to 151.0.7922.109 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Cri

How urgent is CVE-2026-19137?

Priority 35/100. High severity

Software pages

Android vulnerabilities · 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