dbcve.org
ChromeWeb browser · Google

CVE-2026-5289

CRITICAL · 9.6 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 146.0.7680.177 or later.
See remediation →
100/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 Navigation in Google Chrome prior to 146.0.7680.178 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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

Use-after-free vulnerability in Chrome's Navigation component allows a remote attacker with pre-existing renderer process compromise to potentially escape the sandbox via a crafted HTML page. This is a memory safety flaw where a freed memory pointer is accessed after deallocation.

MitigationUpdate Google Chrome to version 146.0.7680.178 or later. Organizations should ensure automated browser patching is enabled or deploy the update through their patch management infrastructure.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Check installed Chrome version
    Navigate to chrome://version in the Chrome address bar or run 'google-chrome --version' (Linux) or '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' (Windows) in a command prompt
    Affected if The displayed version number is lower than 146.0.7680.177
  2. Verify Chrome is the active browser
    Check if Chrome browser process is currently running on the system via Task Manager (Windows) or Activity Monitor/Process Monitor (macOS/Linux)
    Affected if Chrome is actively running and the version from step 1 is in the affected range
  3. Confirm Navigation component is present
    This is a core Chrome component - open chrome://navigation (if available) or inspect running Chrome processes
    Affected if Chrome is running with a vulnerable version from step 1 - the Navigation component exists in all standard Chrome installations
  4. Check browser patch status
    Navigate to chrome://settings/help to see if the browser reports it is up to date, or check if auto-updates are enabled in chrome://settings
    Affected if The browser reports a version below 146.0.7680.177 or indicates updates are pending

You are affected if Chrome is actively used and the installed version is lower than 146.0.7680.177, as this version range contains the use-after-free vulnerability in the Navigation component.

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. Organizations should ensure automated browser patching is enabled or deploy the update through their patch management infrastructure.

Recommended fix High confidence

Chrome 146.0.7680.178 or later

  1. Open Chrome and navigate to Help > About Google Chrome to check the current version
  2. If the version is earlier than 146.0.7680.178, download the latest stable Chrome from the official Chrome download page (google.com/chrome)
  3. Install the update and restart the browser if prompted
  4. Verify the version after update shows 146.0.7680.178 or later
Caveat Chrome security updates are backward compatible with no expected breaking changes for end users

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-5289 — 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-5289 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