dbcve.org
ChromeWeb browser · Google

CVE-2026-7356

HIGH · 8.8 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to 147.0.7727.138 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 Navigation in Google Chrome prior to 147.0.7727.138 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

Use-after-free vulnerability in Google Chrome's Navigation component allows a remote attacker to execute arbitrary code via a crafted HTML page. The flaw occurs when the browser continues to use a freed memory pointer in the navigation handling code, enabling potential code execution in the renderer process context.

MitigationUpgrade Google Chrome to version 147.0.7727.138 or later. Organizations should deploy browser updates through their enterprise patch management systems and verify compliance across managed endpoints.

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:< 147.0.7727.138

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. Check if Google Chrome is installed
    Open Chrome and navigate to chrome://version, or on Windows check C:\Program Files\Google\Chrome\Application\chrome.exe, on macOS check /Applications/Google Chrome.app, on Linux check /opt/google/chrome/chrome
    Affected if Google Chrome is present on the system
  2. Determine the installed Chrome version
    Navigate to chrome://settings/help in the browser address bar. The version number is displayed on that page. Alternatively, run 'chrome --version' from command line on Linux, or right-click chrome.exe and select Properties > Details on Windows
    Affected if Unable to retrieve version information or Chrome is not installed
  3. Compare installed version against the affected range
    The affected versions are any Google Chrome release prior to 147.0.7727.138. Compare your installed version number (from step 2) to this threshold. For example, if your version shows 147.0.7727.100, it is below the patched version
    Affected if Installed version is less than 147.0.7727.138 (for example, 147.0.7727.100, 146.0.6432.45, etc.)
  4. Verify the Navigation component context
    This vulnerability exists in Chrome's Navigation component, which handles page navigation behavior. The vulnerability is triggered by visiting a crafted HTML page. Since this is a core browser component, any browsing activity could potentially trigger the flaw if the malicious page is loaded
    Affected if Chrome with version < 147.0.7727.138 is used for web browsing

You are affected if Google Chrome is installed and its version is lower than 147.0.7727.138, as the use-after-free in the Navigation component would apply during normal browser use.

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 147.0.7727.138 or later
Fixed in 147.0.7727.138
Interim mitigation

Upgrade Google Chrome to version 147.0.7727.138 or later. Organizations should deploy browser updates through their enterprise patch management systems and verify compliance across managed endpoints.

Recommended fix High confidence

Chrome 147.0.7727.138 or later

  1. 1. Open Google Chrome
  2. 2. Navigate to Menu > Help > About Google Chrome
  3. 3. The browser will check for updates automatically
  4. 4. If an update is available, click 'Update Google Chrome'
  5. 5. Restart the browser to complete the installation

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7356 — 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-7356 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