What is CVE-2026-9110?
Inappropriate implementation in UI in Google Chrome on Windows prior to 148.0.7778.179 allowed a remote attacker who had compromised the renderer process to perform UI spoofing via a crafted HTML page. (Chromium security severity: Critical)
The record classifies CVE-2026-9110 under weakness class CWE-451. 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. 4 affected-product entries are recorded, across 4 vendors, listed below. The identifier was first published 161 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 4.2 — MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:L - EPSS (FIRST)
- 0.2% probability of exploitation in the next 30 days, higher than 10.2% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 4.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-05-20
Is CVE-2026-9110 being exploited?
Weaponised exploit code for CVE-2026-9110 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 16 in the Threadlinqs vulnerability feed.
- trickest/cve (trickest)
Affected products and versions
How to fix CVE-2026-9110
Vendor advisory: https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0841193308.html. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.
Threat activity tracking CVE-2026-9110
1 tracked threat in the Threadlinqs corpus references CVE-2026-9110, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, FIRST EPSS, public proof-of-concept repositories. Last verified by Threadlinqs on .