dbcve.org
ChromeWeb browser · Google

CVE-2025-0291

HIGH · 8.8 CVSS v3.1 Published 2025-01-08
Fix available
A fix is available. Upgrade to 131.0.6778.264 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 131.0.6778.264 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 Chrome's V8 JavaScript engine allows a remote attacker to execute arbitrary code via a maliciously crafted HTML page. While the code executes within a sandbox (limiting direct system impact), this still represents a high-severity code execution flaw in a widely-deployed browser component.

MitigationUpdate Google Chrome to version 131.0.6778.264 or later to remediate this vulnerability. Organizations should ensure automated browser patching is enabled.

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

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
    On Windows, check C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. On macOS, check /Applications/Google Chrome.app. On Linux, check /usr/bin/google-chrome or /opt/google/chrome/google-chrome.
    Affected if Google Chrome browser is present on the system
  2. Obtain the installed Chrome version number
    Open Chrome and navigate to chrome://version, or run 'google-chrome --version' on Linux/macOS, or check the version property of the Chrome executable via file properties on Windows.
    Affected if Unable to determine version indicates Chrome may not be properly installed
  3. Compare installed version against the vulnerable range
    Compare the version shown (e.g., 131.0.6778.x) to the safe version 131.0.6778.264. Any version below 131.0.6778.264 (such as 131.0.6778.263, 131.0.6778.200, 130.x.x.x, etc.) is affected.
    Affected if Installed version is less than 131.0.6778.264
  4. Confirm V8 JavaScript engine is in use
    This vulnerability affects the V8 engine which is enabled by default in Chrome. No additional configuration check needed unless using a special Chrome variant without V8.
    Affected if Using a standard Chrome build with V8 enabled (default configuration)

The system is affected if Google Chrome is installed and its version number is lower than 131.0.6778.264, as this is the specific version that contains the fix for this V8 type confusion vulnerability.

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

Update Google Chrome to version 131.0.6778.264 or later to remediate this vulnerability. Organizations should ensure automated browser patching is enabled.

Recommended fix High confidence

131.0.6778.264 (Chrome Stable)

  1. Ensure Chrome is set to automatically update (enabled by default) or manually check for updates
  2. Open Google Chrome and navigate to Menu > Help > About Google Chrome
  3. Chrome will check for available updates and download version 131.0.6778.264 or later
  4. Restart the browser to apply the update
  5. Verify the installed version by returning to Menu > Help > About Google Chrome and confirming the version is 131.0.6778.264 or higher

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-2025-0291 — 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-0291 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