dbcve.org
ChromeWeb browser · Google

CVE-2026-5286

HIGH · 8.8 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 146.0.7680.177 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Use after free in Dawn in Google Chrome prior to 146.0.7680.178 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: High)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A use-after-free vulnerability in Dawn (Google's WebGPU implementation) in Google Chrome versions prior to 146.0.7680.178 allows remote attackers to achieve arbitrary code execution via a specially crafted HTML page that triggers the UAF condition when processing WebGPU operations.

MitigationUpdate Google Chrome to version 146.0.7680.178 or later. As a temporary mitigation, WebGPU can be disabled via chrome://settings under Privacy and Security.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 146.0.7680.177

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Google Chrome is installed
    Check for Chrome installation: On Windows, look in Program Files\Google\Chrome\Application\chrome.exe or %LOCALAPPDATA%\Google\Chrome\Application\chrome.exe. On Mac, check /Applications/Google Chrome.app. On Linux, run 'which google-chrome' or 'which chromium-browser'.
    Affected if Chrome is not installed on the system, then this CVE does not apply.
  2. Identify the installed Chrome version
    Open Chrome and navigate to chrome://version, or click Help > About Google Chrome. Alternatively, run 'google-chrome --version' on Linux or Mac, or check the executable properties on Windows.
    Affected if The installed version is lower than 146.0.7680.177 (for example, 146.0.7680.176, 145.x.x.x, or earlier). Versions 146.0.7680.177 and later are not affected.
  3. Verify WebGPU is enabled
    In Chrome, go to chrome://flags/#enable-webgpu and check if WebGPU is enabled. Also check chrome://flags/#enable-unsafe-webgpu for any experimental settings. In enterprise environments, check the WebGPU policy via chrome://policy.
    Affected if WebGPU is explicitly disabled by policy or flag, then the attack surface is reduced though the browser remains vulnerable if WebGPU is later enabled.
  4. Check for recent Chrome usage
    Review recently opened tabs or browsing history for unfamiliar or suspicious HTML pages. Check chrome://history for the timeframe of potential exploitation.
    Affected if User has visited untrusted or crafted HTML pages while running a vulnerable Chrome version, increasing likelihood of exploitation.

A system is affected if Google Chrome is installed with a version lower than 146.0.7680.177 and WebGPU is enabled or could be enabled, allowing potential exploitation via crafted HTML pages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 146.0.7680.177 or later
Fixed in 146.0.7680.177
Interim mitigation

Update Google Chrome to version 146.0.7680.178 or later. As a temporary mitigation, WebGPU can be disabled via chrome://settings under Privacy and Security.

Recommended fix High confidence

Chrome 146.0.7680.178 or later

  1. Verify current Chrome version by navigating to chrome://settings/help
  2. Close all running Chrome instances
  3. If automatic updates are enabled, Chrome will update automatically on next launch
  4. If manual update is needed, download Chrome from the official website (google.com/chrome) or use the enterprise deployment tools
  5. Restart Chrome after the update completes
  6. Verify the version is now 146.0.7680.178 or later by checking chrome://settings/help

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5286 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5286 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data