dbcve.org
ChromeWeb browser · Google

CVE-2026-17725

HIGH · 8.8 CVSS v3.1 Published 2026-07-30
Fix available
A fix is available. Upgrade to 151.0.7922.72 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 3 weeks old

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 151.0.7922.72 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 Google Chrome's V8 JavaScript engine allows a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. The vulnerability stems from incorrect handling of JavaScript object types in V8, which can be exploited to escape sandbox restrictions.

MitigationUpgrade Google Chrome to version 151.0.7922.72 or later to patch the V8 type confusion vulnerability. Organizations with centralized patch management should deploy the update enterprise-wide.

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

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. Verify Google Chrome is installed
    Check if Google Chrome browser is present on the system. On Windows, look for Chrome in Program Files or the Start Menu. On macOS, check /Applications/Google Chrome. On Linux, run 'which google-chrome' or 'which chrome'.
    Affected if Google Chrome is not installed - this CVE does not apply to other browsers
  2. Determine installed Chrome version via UI
    Open Chrome and navigate to chrome://settings/help (or click Settings > About Chrome). The version number is displayed on that page.
    Affected if Version shown is less than 151.0.7922.72 (e.g., 151.0.7922.71, 150.x.x.x, etc.)
  3. Determine installed Chrome version via command line
    Run 'google-chrome --version' on Linux, 'chrome --version' on ChromeOS, or check the executable properties on Windows. The output displays the full version string.
    Affected if Version output is less than 151.0.7922.72
  4. Confirm V8 engine is in use
    This CVE affects the V8 JavaScript engine which is used by default in Chrome. No configuration check needed - Chrome always uses V8 for JavaScript execution.
    Affected if Using Chrome (V8 is always enabled by default)
  5. Verify Chrome is not running a sandboxed-only variant
    This vulnerability affects standard Chrome installations. The vulnerability is in the V8 engine itself, not in sandboxing. If Chrome runs normally, V8 is active.
    Affected if Standard Chrome installation (not a restricted variant without V8)

You are affected if Google Chrome is installed and the version number is below 151.0.7922.72.

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

Upgrade Google Chrome to version 151.0.7922.72 or later to patch the V8 type confusion vulnerability. Organizations with centralized patch management should deploy the update enterprise-wide.

Recommended fix High confidence

Google Chrome 151.0.7922.72 or later

  1. Open Google Chrome
  2. Navigate to Settings > Help > About Google Chrome
  3. Click 'Check for updates' or wait for automatic update check
  4. If update is available, click 'Restart' to apply the update
  5. Verify the version by returning to About Google Chrome - it should show version 151.0.7922.72 or later

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