CVE-2026-9112 — Google Chrome
As of 2026-05-21, CVE-2026-9112 is a HIGH-severity vulnerability in Google Chrome, CVSS v3.1 8.8, EPSS 0.0% (9.1th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-9112, most recently “Google Chrome Stable 148.0.7778.178/179 — CVE-2026-9111 WebRTC Use-After-Free RCE & CVE-2026-9110 UI Inappropriate Implementation (16 CVEs Patched)”.
Last updated: 2026-05-21
What is CVE-2026-9112?
Use after free in GPU in Google Chrome on Windows prior to 148.0.7778.179 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
The record classifies CVE-2026-9112 under weakness class CWE-416. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 115 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 8.8 — HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - EPSS (FIRST)
- 0.0% probability of exploitation in the next 30 days, higher than 9.1% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 4.8/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-05-20, last modified 2026-05-21
Is CVE-2026-9112 being exploited?
It currently carries a trending score of 9 in the Threadlinqs vulnerability feed.
Affected products and versions
- Google: Chrome
How to fix CVE-2026-9112
No vendor patch reference has been recorded for CVE-2026-9112 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-9112
1 tracked threat in the Threadlinqs corpus references CVE-2026-9112, either in the campaign’s CVE list or as an indicator on the campaign record.
- Google Chrome Stable 148.0.7778.178/179 — CVE-2026-9111 WebRTC Use-After-Free RCE & CVE-2026-9110 UI Inappropriate Implementation (16 CVEs Patched) — CRITICAL · 2026-05-21
Sources
Seeded from cveorg and not yet processed by the Threadlinqs enrichment pipeline, so blank CVSS, EPSS or KEV fields above mean NOT MEASURED rather than measured-absent.
← all vulnerabilities · Markdown version · Threadlinqs Intelligence