dbcve.org
ChromeWeb browser · Google

CVE-2026-7337

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
Type Confusion in V8 in Google Chrome prior to 147.0.7727.138 allowed a remote attacker to execute arbitrary code inside a sandbox 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

Type confusion vulnerability in the V8 JavaScript engine in Google Chrome prior to version 147.0.7727.138 allows a remote attacker to execute arbitrary code via a crafted HTML page. The attack is constrained by Chrome's sandbox, reducing but not eliminating the risk.

MitigationUpdate Google Chrome to version 147.0.7727.138 or later to patch the V8 type confusion vulnerability.

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 installed Chrome version
    Open chrome://version in the Chrome address bar and note the version number displayed under 'Google Chrome'
    Affected if the displayed version is below 147.0.7727.138
  2. Alternative version check via menu
    Click the three-dot menu > Help > About Google Chrome and view the version shown on that page
    Affected if the version shown is less than 147.0.7727.138
  3. Confirm V8 engine is in use
    Verify that JavaScript execution is enabled in the browser settings (default state)
    Affected if JavaScript is enabled and the browser version is below 147.0.7727.138 - the vulnerable V8 engine code is active

You are affected if Google Chrome is running with a version number lower than 147.0.7727.138 and JavaScript is enabled, as the V8 type confusion flaw exists in that engine version.

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

Update Google Chrome to version 147.0.7727.138 or later to patch the V8 type confusion vulnerability.

Recommended fix High confidence

Chrome 147.0.7727.138 or later

  1. Open Google Chrome browser
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. Chrome will automatically check for updates
  6. If version 147.0.7727.138 or later is available, click 'Update Google Chrome'
  7. Restart the browser to apply the update

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation0.5 h
  • Testing1.0 h
  • Review / QA0.5 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-7337 — 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-7337 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