dbcve.org
ChromeWeb browser · Google

CVE-2025-12432

HIGH · 8.8 CVSS v3.1 Published 2025-11-10
Fix available
A fix is available. Upgrade to 142.0.7444.59 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
Race in V8 in Google Chrome prior to 142.0.7444.59 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 race condition exists in the V8 JavaScript engine in Google Chrome versions prior to 142.0.7444.59. This timing vulnerability allows a remote attacker to exploit heap corruption through a specially crafted HTML page, potentially leading to arbitrary code execution.

MitigationUpdate Google Chrome to version 142.0.7444.59 or later. Organizations should deploy the browser update through their patch management systems and verify complete coverage across all 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:< 142.0.7444.59

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 installed Chrome version
    Open Google Chrome and navigate to chrome://version, or run 'google-chrome --version' (Linux/macOS) or 'chrome --version' (Windows) in terminal/command prompt
    Affected if The displayed version number is less than 142.0.7444.59 (for example, 142.0.7444.50 or earlier)
  2. Confirm Chrome channel
    On chrome://version page, look at the 'Chrome is up to date' message or check the 'Installation channel' field to confirm this is a stable channel build
    Affected if The channel shows stable and version is below 142.0.7444.59

You are affected if you are running Google Chrome stable version prior to 142.0.7444.59 on any supported platform.

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

Update Google Chrome to version 142.0.7444.59 or later. Organizations should deploy the browser update through their patch management systems and verify complete coverage across all endpoints.

Recommended fix High confidence

Chrome 142.0.7444.59

  1. Check current Chrome version by navigating to chrome://settings/help
  2. Navigate to the Chrome download page at google.com/chrome or use the system's package manager
  3. Download and install Chrome version 142.0.7444.59 or later
  4. Restart Chrome to complete the update
  5. Verify the installed version is 142.0.7444.59 or higher via chrome://settings/help

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

Fix this in Chrome Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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