dbcve.org
ChromeWeb browser · Google

CVE-2025-6191

HIGH · 8.8 CVSS v3.1 Published 2025-06-18
Fix available
A fix is available. Upgrade to 137.0.7151.119 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 137.0.7151.119 allowed a remote attacker to potentially perform out of bounds memory access 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 137.0.7151.119 allows remote attackers to achieve out-of-bounds memory access via malicious HTML pages. The overflow occurs during integer operations in the JavaScript engine, potentially enabling memory corruption or information disclosure.

MitigationUpdate Google Chrome to version 137.0.7151.119 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:< 137.0.7151.119

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 Chrome version
    Navigate to chrome://settings/help or type 'About Google Chrome' in the address bar to display the current version number
    Affected if The displayed version is older than 137.0.7151.119 (for example, 136.x.x.x or earlier)
  2. Verify V8 engine presence
    The V8 JavaScript engine is built into Chrome and cannot be disabled; this check confirms the vulnerable component exists
    Affected if Chrome is installed and functional (V8 is always present in any Chrome installation)

You are affected if your installed Chrome version is lower than 137.0.7151.119, as the integer overflow vulnerability exists in the V8 engine of all earlier versions.

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

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

Recommended fix High confidence

Chrome version 137.0.7151.119 or later

  1. 1. Open Google Chrome browser
  2. 2. Click the Chrome menu (three vertical dots) in the top-right corner
  3. 3. Select 'Help' from the dropdown menu
  4. 4. Click 'About Google Chrome'
  5. 5. Chrome will automatically check for and download available updates
  6. 6. Wait for the update to download and install
  7. 7. Click 'Relaunch' to restart Chrome and apply the update

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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