# CVE-2026-5281: Google Dawn Use-After-Free

> A remote attacker with compromised renderer access can execute arbitrary code via a crafted HTML page in Google Chrome.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 1 Apr 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Apr 2026
- **Updated:** 2 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-5281, GHSA-xf76-839h-pfpm, MINI-3j4m-hj42-j99f

## What is CVE-2026-5281?

CVE-2026-5281 is a high-severity use after free vulnerability in Google Chrome, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Use after free in Dawn in Google Chrome prior to 146.0.7680.178 allowed a remote attacker who had compromised the renderer process to execute arbitrary code via a crafted HTML page. (Chromium security severity: High)

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-5281?

It affects 1 product.


Products: Google Chrome.

## How do I fix CVE-2026-5281?

Upgrade to a fixed version. US federal agencies must fix it by 15 Apr 2026.

## Is CVE-2026-5281 being exploited?

Yes. Attackers have exploited CVE-2026-5281 in the wild since at least 1 Apr 2026.

Public exploit code:

- Chrome WebGPU Use-After-Free (CWE-416)  This toolkit is for security research and defensive verification around CVE-2026-5281. Patched Chrome version: 146.0.7680.178 Potentially vulnerable versions: anything below 146.0.7680.178 (github_poc): https://github.com/umair-aziz025/CVE-2026-5281-Research-Toolkit
- CVE-2026-5281 (Chrome Dawn WebGPU UAF) analysis, lab validation tools, and reproducible environment for vulnerable vs patched builds. (github_poc): https://github.com/TheMalwareGuardian/CVE-2026-5281
- https://github.com/jaf0rk/CVE-2026-5281 (github_poc): https://github.com/jaf0rk/CVE-2026-5281
- https://github.com/jaf0rk/CVE-2026-5281-CVE-2026-11057-fullchain (github_poc): https://github.com/jaf0rk/CVE-2026-5281-CVE-2026-11057-fullchain

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5281 and fix it if it is affected.

What it is: CVE-2026-5281 is a high-severity use after free vulnerability in Google Chrome, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2026-5281 in the wild since at least 1 Apr 2026.

Affected product: Google Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5281/ (Markdown: https://insights.sbomify.com/CVE-2026-5281/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5281
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5281
- OSV: https://osv.dev/vulnerability/CVE-2026-5281

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5281/
Summaries are generated and may contain mistakes; the official description above is the record.