Vulnerability record · CVE-2026-5281 · published 1 April 2026
CVE-2026-5281: Google Chrome Dawn use-after-free allows remote code execution
Google · Chrome
Chrome versions before 146.0.7680.178 contain a use-after-free flaw in the Dawn graphics component. An attacker who has already compromised the renderer process can trigger the bug with a crafted HTML page and execute arbitrary code. It matters because Chrome is widely deployed and CISA added this to its Known Exploited Vulnerabilities catalog.
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)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Automated analysis
high priorityKnown exploitation per CISA KEV and a high CVSS of 8.8, though exploitation requires a pre-compromised renderer, which limits standalone reach.
What it is
Chrome versions before 146.0.7680.178 contain a use-after-free flaw in the Dawn graphics component. An attacker who has already compromised the renderer process can trigger the bug with a crafted HTML page and execute arbitrary code. It matters because Chrome is widely deployed and CISA added this to its Known Exploited Vulnerabilities catalog.
Impact
An attacker gains arbitrary code execution in the browser context, with high impact to confidentiality, integrity and availability. The CVSS vector requires the renderer to already be compromised, so the flaw is a sandbox-escape or post-compromise escalation primitive rather than a standalone entry point.
Attack surface
Reached over the network through a crafted HTML page, requiring user interaction (UI:R) and no privileges (PR:N). The description states the attacker must already have compromised the renderer process, so this is not exploitable from a clean browsing session alone.
Exploitation
Listed in CISA KEV with a due date of 2026-04-15, indicating known exploitation in the wild. EPSS 30-day probability is about 4.9 percent (91.7th percentile), and no ransomware campaign use is documented.
What to do
- Upgrade Chrome to 146.0.7680.178 or later as the primary fix.
- Apply the vendor advisory and CISA BOD 22-01 required actions; discontinue use if mitigations are unavailable.
- Enforce automatic browser updates and verify version compliance across managed endpoints.
- Restrict or isolate high-risk browsing and treat renderer compromise as a serious escalation path.
- Monitor Chromium issue 491518608 and the Chrome release blog for follow-up guidance.
Detection
- Alert on Chrome versions below 146.0.7680.178 in asset inventories and endpoint telemetry.
- Hunt for renderer process crashes or abnormal memory behavior tied to Dawn/graphics activity.
- Look for suspicious child processes or code execution originating from Chrome renderer processes.
- Correlate web proxy or DNS logs for crafted HTML delivery against hosts running vulnerable Chrome builds.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Exploitation in the wild
CISA added CVE-2026-5281 to the Known Exploited Vulnerabilities catalog on 1 April 2026 as "Google Dawn Use-After-Free Vulnerability". 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. Federal deadline 15 April 2026.
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_31.html | Vendor Advisory |
| https://issues.chromium.org/issues/491518608 | Issue TrackingPermissions Required |
| https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-5281 | US Government Resource |
Track CVE-2026-5281 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2026-5281), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.