dbcve.org
ChromeWeb browser · Google

CVE-2025-10500

HIGH · 8.8 CVSS v3.1 Published 2025-09-24
Fix available
A fix is available. Upgrade to 140.0.7339.185 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 140.0.7339.185 allowed a remote attacker to potentially exploit heap corruption 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 exists in Dawn (Google's WebGPU implementation) in Google Chrome versions prior to 140.0.7339.185. An attacker can trigger this flaw by enticing a user to visit a crafted HTML page, causing the browser to access freed memory and potentially achieve heap corruption with potential for arbitrary code execution.

MitigationUpdate Google Chrome to version 140.0.7339.185 or later. Organizations should deploy the browser update through their standard patch management processes and verify completion across affected 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:< 140.0.7339.185

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
    On Windows, check for Chrome in C:\Program Files\Google\Chrome\Application\chrome.exe or via Registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome. On macOS, check /Applications/Google Chrome.app. On Linux, check /opt/google/chrome/chrome or via package manager.
    Affected if Chrome is not found on the system, so the CVE does not apply.
  2. Determine installed Chrome version
    Open Chrome and navigate to chrome://version, or right-click chrome.exe and select Properties > Details > File Version, or run 'google-chrome --version' on Linux.
    Affected if The detected version number is lower than 140.0.7339.185.
  3. Verify WebGPU is accessible
    In Chrome, navigate to chrome://flags/#enable-webgpu or check if WebGPU appears in chrome://gpu. WebGPU may also be detected via developer tools Console by running 'navigator.gpu'.
    Affected if WebGPU is enabled or accessible in the browser, making the attack surface active.
  4. Confirm Chrome is in use as the primary browser
    Check default browser settings or interview users to determine if Chrome is regularly used for web browsing.
    Affected if Users actively use Google Chrome for browsing untrusted websites, increasing exposure to the crafted HTML attack vector.

A user is affected if Google Chrome versions prior to 140.0.7339.185 are installed and WebGPU is accessible in the browser environment.

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

Update Google Chrome to version 140.0.7339.185 or later. Organizations should deploy the browser update through their standard patch management processes and verify completion across affected endpoints.

Recommended fix High confidence

Chrome 140.0.7339.185 or later

  1. Open Google Chrome
  2. Click the three-dot menu (top right)
  3. Select 'Help' > 'About Google Chrome'
  4. Chrome will check for updates and automatically download version 140.0.7339.185 or later
  5. Click 'Restart' to apply the update
  6. Verify the version by returning to 'About Google Chrome' - it should show 140.0.7339.185 or higher

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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