webgpu

Google appears to be building a way to switch off the browser’s WebGPU engine on devices running Android 16 as part of the operating system’s new Advanced Protection Mode, a move that signals both the maturing importance of GPU-accelerated web APIs and the continued security headaches they can...

The Chromium project fixed a high‑severity memory-corruption bug in its WebGPU shader compiler (Tint) — tracked as CVE‑2026‑3062 — and Microsoft has recorded that upstream fix in its Security Update Guide so Edge users can confirm when their browser is no longer vulnerable. In short: this is a...

Google’s December stable update corrected two high‑severity Chromium issues — a use‑after‑free in WebGPU (CVE‑2025‑14765) and an out‑of‑bounds read/write in V8 (CVE‑2025‑14766) — and the fixes were rolled into Chrome stable (143.0.7499.146/.147), with downstream consumers such as Microsoft Edge...

Chromium’s CVE-2025-12725 — an out‑of‑bounds write reachable via WebGPU — appears in Microsoft’s Security Update Guide because Microsoft Edge (the Chromium‑based Edge) consumes the upstream Chromium open‑source engine; Microsoft uses the Security Update Guide to record upstream Chromium CVEs...

Google’s September stable update for Chrome closed a notable Use‑After‑Free (UAF) in the Dawn WebGPU implementation — tracked as CVE‑2025‑10500 — alongside several other high‑severity graphics and engine fixes; Windows users and administrators running Microsoft Edge (Chromium‑based) should treat...