CVE-2026-9124 — Google Chrome
As of 2026-05-20, CVE-2026-9124 is a MEDIUM-severity vulnerability in Google Chrome, CVSS v3.1 5.3, EPSS 0.0% (18.5th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-9124, 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-20
What is CVE-2026-9124?
Insufficient validation of untrusted input in Input in Google Chrome on prior to 148.0.7778.179 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
The record classifies CVE-2026-9124 under weakness class CWE-20. 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. 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
- 5.3 — MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N - EPSS (FIRST)
- 0.0% probability of exploitation in the next 30 days, higher than 18.5% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 3.4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-05-20
Is CVE-2026-9124 being exploited?
It currently carries a trending score of 11 in the Threadlinqs vulnerability feed.
Affected products and versions
- Google: Chrome
How to fix CVE-2026-9124
No vendor patch reference has been recorded for CVE-2026-9124 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-9124
1 tracked threat in the Threadlinqs corpus references CVE-2026-9124, 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