dbcve.org
ChromeWeb browser · Google

CVE-2025-13228

HIGH · 8.8 CVSS v3.1 Published 2025-11-18
Fix available
A fix is available. Upgrade to 142.0.7444.59 / 142.0.7444.60 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 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

This is a type confusion vulnerability in the V8 JavaScript engine used by Google Chrome. The flaw allows a remote attacker to cause the browser to misinterpret object types, leading to heap corruption, which can potentially be exploited for arbitrary code execution through a malicious HTML page.

MitigationUpdate Google Chrome to version 142.0.7444.59 or later to patch the vulnerability. Organizations should deploy browser updates through their patch management systems.

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< 142.0.7444.60

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 for Chrome in Program Files or via 'Get-ItemProperty' registry key. On macOS, check /Applications/Google Chrome.app. On Linux, check /usr/bin/google-chrome or via package manager.
    Affected if Google Chrome browser is present on the system
  2. Retrieve installed Chrome version
    Navigate to chrome://version in the Chrome browser address bar, or run 'google-chrome --version' from command line on Linux/macOS, or check Add/Remove Programs on Windows.
    Affected if Unable to determine version indicates potential unpatched installation
  3. Compare version against vulnerable range
    Note the full version number (e.g., 141.0.6545.99) and compare the first three numeric segments to 142.0.7444.59. Any version below 142.0.7444.59 is affected.
    Affected if Version number is less than 142.0.7444.59 (e.g., 142.0.7444.58, 141.x.x.x, 140.x.x.x, etc.)
  4. Verify V8 engine presence
    The vulnerability exists in the V8 JavaScript engine bundled with Chrome. This is confirmed by the Chrome version check above; V8 is included by default in all Chrome installations.
    Affected if Chrome is installed (V8 is always present as the JavaScript engine)
  5. Check for auto-update status
    Navigate to chrome://settings/help to see if updates are available or if the browser is up to date. On enterprise-managed systems, check group policy or MDM enrollment for browser update management.
    Affected if Browser shows update available or reports version below current stable release

If the installed Google Chrome version is below 142.0.7444.59, the environment is vulnerable to this type confusion flaw in the V8 engine.

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 / 142.0.7444.60 or later
Fixed in 142.0.7444.59142.0.7444.60
Interim mitigation

Update Google Chrome to version 142.0.7444.59 or later to patch the vulnerability. Organizations should deploy browser updates through their patch management systems.

Recommended fix High confidence

Chrome 142.0.7444.59 (or later stable release)

  1. Open Google Chrome browser
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. Chrome will automatically check for updates and download version 142.0.7444.59 or later
  6. Click 'Relaunch' to restart the browser and apply the update
  7. Verify the update by returning to About Google Chrome and confirming the version displays 142.0.7444.59 or higher
Caveat No breaking changes expected; browser settings and preferences are preserved during upgrade

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-13228 — 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-13228 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