Google Dawn Use-After-Free Vulnerability
Google — Chrome
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)
8.8
4.9%
Vector breakdown
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Published
- Apr 1, 2026
- Modified
- Jul 24, 2026
- Added to KEV
- Apr 1, 2026
- Federal patch due
- Apr 15, 2026
CISA required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Weakness classification
Affected packages
Proof-of-concept & exploitation references
6 foundWeaponization
Public repositories whose name or description references CVE-2026-5281, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
- umair-aziz025/CVE-2026-5281-Research-Toolkit★ 4
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
updated Jun 21, 2026
- TheMalwareGuardian/CVE-2026-5281★ 2
CVE-2026-5281 (Chrome Dawn WebGPU UAF) analysis, lab validation tools, and reproducible environment for vulnerable vs patched builds.
updated Jul 23, 2026
- iqx6889/CVE-2026-52813-Gogs-RCE★ 1
CVE-2026-52813 (Gogs Path Traversal → Git Hooks RCE) defensive writeup: root-cause & patch analysis, Sigma/SIEM detection rules, IOCs, non-intrusive version scanner. No weaponized PoC.
updated Jul 21, 2026
- jaf0rk/CVE-2026-5281-CVE-2026-11057-fullchain★ 1
updated Aug 28, 2026
- jaf0rk/CVE-2026-5281★ 0
updated Jul 18, 2026
- HORKimhab/CVE-2026-52810★ 0
CVE-2026-52810 - Draft or TODO
updated Sep 3, 2026
References
Frequently asked questions
What is CVE-2026-5281?
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)
How severe is CVE-2026-5281?
CVE-2026-5281 has a CVSS base score of 8.8 out of 10 (CVSS 3.1).
Is CVE-2026-5281 actively exploited in the wild?
Yes. CVE-2026-5281 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Apr 1, 2026, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2026-5281?
4.9% - meaning FIRST.org's EPSS model estimates a 4.9% probability this vulnerability will be exploited in the wild within 30 days (92% percentile among all scored CVEs).
Is there exploit tooling available for CVE-2026-5281?
We found 6 public GitHub repositories referencing CVE-2026-5281, though none matched a known Nuclei template or Metasploit module at last check. Review each one before relying on it - see the proof-of-concept section above.
What type of vulnerability is CVE-2026-5281?
CVE-2026-5281 is classified under CWE-416 (Use after free).
Cross-checked against
Impactr finds and proves whether CVE-2026-5281 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.
Join the waitlist