CVE-2026-8555: Use after free in GTK in Google Chrome on Windows prior to 148.0.7778.168 allowed a remote attacker to execute

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

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

Q: Is CVE-2026-8555 being exploited?

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

CVE-2026-8555 affects chrome. Severity is high (CVSS 8.8). Use after free in GTK in Google Chrome on Windows prior to 148.0.7778.168 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: High)

Routine

HIGH 8.8UPGRADE

CVE-2026-8555 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 GTK in Google Chrome on Windows prior to 148.0.7778.168 allowed a remote attacker to execute arbitrary code 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.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 80%)
CISA exploited list	No
Weakness	CWE-416
Published	2026-05-14
Last modified	2026-10-26

Publisher (CNA): Chrome · Vendor: google

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-14 20:17 UTCPublished CVE record published
2026-10-26 14:10 UTCUpdated Record last modified

google chrome UPGRADE

Affected: < 148.0.7778.168

Fixed in: 148.0.7778.168

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 148.0.7778.168 (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.

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

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

Is CVE-2026-8555 being exploited?

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

CVE-2026-8555 affects chrome. Severity is high (CVSS 8.8). Use after free in GTK in Google Chrome on Windows prior to 148.0.7778.168 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: High)

How urgent is CVE-2026-8555?

Priority 36/100. High severity

Software pages

Windows vulnerabilities · Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-7898 HIGH 8.8 UPGRADE Use after free in Chromoting in Google Chrome on Linux prior to 148.0.7778.96 allowed a remote attacker to exe
CVE-2026-7951 HIGH 8.8 UPGRADE Out of bounds write in WebRTC in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to execute arb
CVE-2026-7992 HIGH 8.8 UPGRADE Insufficient validation of untrusted input in UI in Google Chrome on Linux, ChromeOS prior to 148.0.7778.96 al
CVE-2026-7902 HIGH 8.8 UPGRADE Out of bounds memory access in V8 in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to execute
CVE-2026-7928 HIGH 8.8 UPGRADE Use after free in WebRTC in Google Chrome on Windows prior to 148.0.7778.96 allowed a remote attacker to execu

References

← Back to latest CVEs