dbcve.org
ChromeWeb browser · Google

CVE-2025-10891

HIGH · 8.8 CVSS v3.1 Published 2025-09-24
Fix available
A fix is available. Upgrade to 140.0.7339.207 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
Integer overflow in V8 in Google Chrome prior to 140.0.7339.207 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

Integer overflow in V8 JavaScript engine in Google Chrome prior to 140.0.7339.207 allows remote attackers to trigger heap corruption via malicious HTML pages containing specially crafted JavaScript that causes integer overflow in memory allocation operations.

MitigationUpdate Google Chrome to version 140.0.7339.207 or later to patch the V8 integer overflow 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:< 140.0.7339.207

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. Confirm Google Chrome is installed
    Check for Chrome executable - on Windows look in Program Files\Google\Chrome\Application\chrome.exe, on macOS check /Applications/Google Chrome.app, or on Linux check /usr/bin/google-chrome
    Affected if Chrome is not installed on the system
  2. Determine installed Chrome version
    Open Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/help, or run 'google-chrome --version' in terminal
    Affected if The displayed version number is lower than 140.0.7339.207
  3. Verify V8 engine is in use
    The vulnerability affects the V8 JavaScript engine which is always active when Chrome renders HTML pages; no additional configuration check needed
    Affected if Chrome processes any HTML content with JavaScript enabled

A system is affected if Google Chrome is installed and its version is below 140.0.7339.207, since the integer overflow in V8 triggers when processing crafted HTML pages with JavaScript.

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.207 or later
Fixed in 140.0.7339.207
Interim mitigation

Update Google Chrome to version 140.0.7339.207 or later to patch the V8 integer overflow vulnerability.

Recommended fix High confidence

140.0.7339.207

  1. Open Google Chrome
  2. Navigate to Help > About Google Chrome
  3. The browser will check for updates automatically
  4. If an update is available, click 'Update Google Chrome'
  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
  • 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-10891 — 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-10891 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