dbcve.org
ChromeWeb browser · Google

CVE-2025-14766

HIGH · 8.8 CVSS v3.1 Published 2025-12-16
Fix available
A fix is available. Upgrade to 143.0.7499.146 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
Out of bounds read and write in V8 in Google Chrome prior to 143.0.7499.147 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

Out-of-bounds memory read and write vulnerability in the V8 JavaScript engine in Google Chrome prior to version 143.0.7499.147 allows a remote attacker to corrupt heap memory via a specially crafted HTML page, potentially leading to arbitrary code execution.

MitigationUpdate Google Chrome to version 143.0.7499.147 or later to patch the V8 vulnerability. Organizations should deploy the update through their standard patch management processes.

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

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
    On Windows, check C:\Program Files\Google\Chrome\Application\chrome.exe or search for Chrome in Start menu. On Mac, check /Applications/Google Chrome. On Linux, run 'which google-chrome' or check /usr/bin/google-chrome.
    Affected if Chrome is not found on the system (not vulnerable, not applicable)
  2. Retrieve the installed Chrome version
    Open Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' from command line. On Windows PowerShell: (Get-Item 'C:\Program Files\Google\Chrome\Application\chrome.exe').VersionInfo.ProductVersion
    Affected if Unable to determine version (verification incomplete)
  3. Compare version against affected range
    Compare the installed version number to 143.0.7499.146. The version must be exactly 143.0.7499.146 or higher to be patched. Any version below this (e.g., 143.0.7499.145, 143.0.7499.100, 142.x.x.x) is within the affected range.
    Affected if Installed version is less than 143.0.7499.146 (vulnerable)
  4. Verify JavaScript engine is enabled
    This vulnerability affects Chrome's V8 JavaScript engine. V8 is enabled by default in Chrome and cannot be disabled through standard settings. No manual check needed - V8 is always active for page rendering.
    Affected if N/A - V8 is always enabled in Chrome (vulnerability applies by default if version is affected)

A system is affected if Google Chrome is installed with a version lower than 143.0.7499.146; the V8 JavaScript engine is always enabled in Chrome, so no additional configuration check is required.

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

Update Google Chrome to version 143.0.7499.147 or later to patch the V8 vulnerability. Organizations should deploy the update through their standard patch management processes.

Recommended fix High confidence

Chrome 143.0.7499.146 or later

  1. Open Google Chrome browser
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Help' > 'About Google Chrome'
  4. Chrome will automatically check for and download updates
  5. The update to version 143.0.7499.146 or later will be listed
  6. Click 'Relaunch' or restart the browser to apply the update

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

Fix this in Chrome Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
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,624.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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