Chrome Zero-Day Vulnerability CVE-2026-5281 Fix Guide 2026 Edition
docTechnical analysis of Chrome zero-day vulnerabilities CVE-2026-5281, CVE-2026-2441, CVE-2026-3909, and CVE-2026-3910 — affected 3.5 billion users in 2026. Get CVSS scores, fixed versions, attack chain breakdowns, and enterprise mitigation policies.
CVE-2026-5281 is a use-after-free vulnerability in Dawn, Chrome's WebGPU implementation, rated CVSS 8.8 at High severity and fixed in an emergency release on April 1, 2026. It was the fourth Chrome zero-day disclosed in 2026, and it was added to the CISA Known Exploited Vulnerabilities catalog on the same day the fix shipped. This guide covers the affected versions, the exploit chain, why the GPU stack is a growing target, and the practical steps to take on Windows, macOS, and Linux endpoints.
The vulnerability at a glance
| Field | Value |
|---|---|
| CVE identifier | CVE-2026-5281 |
| Affected component | Dawn, Chrome's WebGPU implementation |
| Weakness class | Use-after-free, CWE-416 |
| CVSS score | 8.8 |
| Severity level | High |
| Fix date | April 1, 2026 |
| Affected versions | Chrome earlier than 146.0.7680.178 on Windows, macOS, and Linux |
| KEV status | Added to the CISA Known Exploited Vulnerabilities catalog the same day; federal agencies faced an April 15 remediation deadline |
| Zero-day count | Fourth Chrome zero-day of 2026 |
| Public proof of concept | None published |
| Related fixes in the same batch | Other issues across the CVE-2026-5272 to 5292 range were addressed in the same release |
How the exploit chain works
A use-after-free means the program keeps a pointer to memory after that memory has been released, then reuses it later. If an attacker controls what occupies that memory in between, the stale reference can be directed to operate on attacker-chosen data.
The disclosed chain does not break out of the browser sandbox directly. The first step is compromising the renderer process, which handles page content inside a sandboxed layer. From there, a maliciously constructed WebGPU page drives the Dawn component into the memory-safety flaw. Success in that condition can lead to arbitrary code execution in the more privileged browser layers beyond the renderer.
The target is therefore reached through normal web browsing: visiting the crafted page is what puts the renderer and the GPU component in play. No local install and no extension action is required as part of the described chain.
Why the WebGPU stack became an attack surface
WebGPU exists to give web pages direct access to graphics hardware, and that design bridges several layers that used to stay separated. The browser talks to driver code, manages shared memory between processes, and runs native-level rendering operations that were previously confined to installed applications. Each of those bridges adds code paths that memory-safety bugs can affect.
The Dawn component sits between JavaScript-level graphics calls and the underlying platform implementation on each operating system. A flaw there crosses the boundary between sandboxed web content and the native graphics stack, which is what raises a renderer-condition bug to the level of a High-severity zero-day. Earlier browser zero-days concentrated in JavaScript engines and media parsing; the steady expansion of GPU and acceleration interfaces means new native-code surfaces appear every year.
No public proof of concept does not mean it is safe
With no public PoC available, defenders cannot test the flaw against their own systems. But the KEV listing is the relevant signal here: it records that the vulnerability is being exploited in real campaigns, regardless of whether exploit code has been published. PoC publication often lags behind active use, and an undisclosed exploit held by an operator is harder to detect than a public one.
The April 15 deadline set for federal agencies reflects that distinction: cataloged, actively exploited flaws are remediated on a short clock even without public details of the technique.
What to do now
- Update Chrome to version 146.0.7680.178 or later on every Windows, macOS, and Linux endpoint, then restart the browser so the new code is actually loaded; a background update that has not been restarted leaves the old build running.
- Check the version from the browser's about or settings page, rather than assuming the update already applied.
- Review installed extensions for anything unused or unfamiliar; extensions are a separate exposure channel, though not part of this exploit chain.
- Organizations should confirm internet-facing endpoints were patched before the KEV deadline, and review sign-in and extension logs for signs of suspicious sessions.
- Keep monitoring the KEV catalog: the other issues fixed in the same 5272 to 5292 release range should be triaged alongside this one.
Frequently asked questions
Am I affected if I am on an older Chrome build but never visited an unusual site?
The affected build is any version earlier than 146.0.7680.178 on the three desktop platforms. Exploitation requires the crafted page to load, so the risk depends on exposure, but unpatched endpoints remain reachable by any campaign that distributes such a page. Updating removes the condition.
Does this zero-day affect mobile Chrome?
The disclosed advisory covers Windows, macOS, and Linux desktop builds. Mobile platforms run on their own release tracks and should be kept updated through the app store, but the specific affected version range listed here applies to the desktop channel.
Why is a WebGPU flaw rated High when browsers already sandbox the renderer?
The renderer sandbox limits what a compromised page can do on its own; the use-after-free in the GPU component is what the chain uses to reach privileged native layers. The High rating reflects the path from a visited web page to code execution, not a single isolated memory bug.