What is CVE-2026-4675?
Heap buffer overflow in WebGL in Google Chrome prior to 146.0.7680.165 allowed a remote attacker to perform an out-of-bounds memory read via a crafted HTML page. The vulnerability resides in Chrome's WebGL graphics rendering component and was reported by the same pseudonymous researcher (_86ac1f1587b71893ed2ad792cd7dde32_) who discovered CVE-2026-5281 (Dawn WebGPU use-after-free zero-day under active exploitation) and CVE-2026-4676 (Dawn use-after-free with sandbox escape potential). This cluster of GPU-layer vulnerabilities suggests systematic fuzzing or targeted research into Chrome's graphics subsystem. The flaw was patched on March 23, 2026 as part of a Chrome Stable Channel update. All Chromium-based browsers including Microsoft Edge, Brave, Opera, and Vivaldi were affected until they incorporated the upstream fix.
The record classifies CVE-2026-4675 under weakness classes CWE-122, CWE-787. 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. 5 affected-product entries are recorded, across 5 vendors, listed below. The identifier was first published 195 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 22.2% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 5.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-03-24
Is CVE-2026-4675 being exploited?
It currently carries a trending score of 16 in the Threadlinqs vulnerability feed.
Affected products and versions
How to fix CVE-2026-4675
The record marks a vendor fix as available for CVE-2026-4675. Patch reference: https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_23.html. Vendor advisory: https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_23.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-4675
No threat campaign in the Threadlinqs corpus currently references CVE-2026-4675, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Seeded from threat-derived and not yet processed by the Threadlinqs enrichment pipeline, so blank CVSS, EPSS or KEV fields above mean NOT MEASURED rather than measured-absent.