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

Q: How do I fix CVE-2026-5281?

chrome: upgrade to 146.0.7680.177. Exact commands for each OS are on this page.

Q: Is CVE-2026-5281 being exploited?

Yes. CVE-2026-5281 is on the CISA Known Exploited Vulnerabilities list, so treat it as patch-now.

Q: What does CVE-2026-5281 affect?

CVE-2026-5281 affects chrome. Severity is high (CVSS 8.8). 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)

Q: How urgent is CVE-2026-5281?

Priority 80/100. High severity; EPSS top 4%: very likely to be exploited; Exploited in the wild (CISA KEV)

Patch now

HIGH 8.8EXPLOITEDUPGRADE

CVE-2026-5281 is a high-severity flaw (CVSS 8.8) affecting chrome, reported as exploited in the wild. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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)

Why this priority

High severity
EPSS top 4%: very likely to be exploited
Exploited in the wild (CISA KEV)

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	13.5% (top 4%)
CISA exploited list	Yes, fix due 2026-04-15
Weakness	CWE-416
Published	2026-04-01
Last modified	2026-07-24

Publisher (CNA): Chrome · Vendor: google

Last updated 2026-07-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-01Exploited Added to the CISA Known Exploited Vulnerabilities list
2026-04-01 05:16 UTCPublished CVE record published
2026-04-15Deadline CISA due date for US federal agencies to patch
2026-07-24 21:10 UTCUpdated Record last modified

google chrome UPGRADE

Affected: < 146.0.7680.177

Fixed in: 146.0.7680.177

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy chrome || rpm -q chrome || chrome --version

2. UPGRADE to 146.0.7680.177 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade chrome

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade chrome

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Exact fixes by distribution

Fedora 46 · python-googleapis-common-protos · FIXED · 1.75.5-1.fc46~bootstrap · FEDORA-2026-d911c4c4e6 · source

sudo dnf upgrade --advisory=FEDORA-2026-d911c4c4e6

Fedora ELN · see advisory · FIXED · FEDORA-2026-e3987c278f · source

sudo dnf upgrade --advisory=FEDORA-2026-e3987c278f

Debian 12 · chromium · FIXED · 146.0.7680.177-1~deb12u1

sudo apt update && sudo apt install --only-upgrade chromium dpkg --compare-versions "$(dpkg-query -W -f='${Version}' chromium)" ge "146.0.7680.177-1~deb12u1" && echo PATCHED || echo STILL-VULNERABLE

Debian 13 · chromium · FIXED · 146.0.7680.177-1~deb13u1

sudo apt update && sudo apt install --only-upgrade chromium dpkg --compare-versions "$(dpkg-query -W -f='${Version}' chromium)" ge "146.0.7680.177-1~deb13u1" && echo PATCHED || echo STILL-VULNERABLE

Alpine 3.23 · qt6-qtwebengine · FIXED · qt6-qtwebengine-6.10.1-r14

apk add --upgrade qt6-qtwebengine apk info -v qt6-qtwebengine

Alpine 3.24 · qt6-qtwebengine · FIXED · qt6-qtwebengine-6.10.2-r13

apk add --upgrade qt6-qtwebengine apk info -v qt6-qtwebengine

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

GitHub PoC: umair-aziz025/CVE-2026-5281-Research-Toolkit (4 stars)
GitHub PoC: TheMalwareGuardian/CVE-2026-5281 (2 stars)
GitHub PoC: jaf0rk/CVE-2026-5281 (0 stars)
Write-up: issues.chromium.org/issues/491518608

Verify at the official source NVD · CVE Program · CISA KEV catalog · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-5281?

chrome: upgrade to 146.0.7680.177. Exact commands for each OS are on this page.

Is CVE-2026-5281 being exploited?

Yes. CVE-2026-5281 is on the CISA Known Exploited Vulnerabilities list, so treat it as patch-now.

What does CVE-2026-5281 affect?

CVE-2026-5281 affects chrome. Severity is high (CVSS 8.8). 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 urgent is CVE-2026-5281?

Priority 80/100. High severity; EPSS top 4%: very likely to be exploited; Exploited in the wild (CISA KEV)

Software pages

Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-0628 HIGH 8.8 UPGRADE Insufficient policy enforcement in WebView tag in Google Chrome prior to 143.0.7499.192 allowed an attacker wh
CVE-2026-5285 HIGH 8.8 UPGRADE Use after free in WebGL in Google Chrome prior to 146.0.7680.178 allowed a remote attacker to execute arbitrar
CVE-2026-6315 HIGH 8.8 UPGRADE Use after free in Permissions in Google Chrome on Android prior to 147.0.7727.101 allowed a remote attacker wh
CVE-2026-6363 HIGH 8.8 UPGRADE Type Confusion in V8 in Google Chrome prior to 147.0.7727.101 allowed a remote attacker to potentially perform
CVE-2026-6311 HIGH 8.3 UPGRADE Uninitialized Use in Accessibility in Google Chrome on Windows prior to 147.0.7727.101 allowed a remote attack

References

← Back to latest CVEs