dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 10 Dec 2025.
ChromeWeb browser · Google

CVE-2025-13223

HIGH · 8.8 CVSS v3.1 Published 2025-11-17
Fix available
A fix is available. Upgrade to 142.0.7444.175 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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.175 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

Type confusion in V8 JavaScript engine allows a remote attacker to exploit heap corruption via a crafted HTML page. The vulnerability stems from improper type handling in V8 that can cause the engine to misuse object types, leading to memory corruption that can be leveraged for code execution.

MitigationUpdate Google Chrome to version 142.0.7444.175 or later. Organizations should ensure endpoint protection and browser update deployment across all managed devices.

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.175
CadraApplication
Affected:all versions

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. Find installed Google Chrome version
    Open Chrome, click the three-dot menu > Help > About Google Chrome. The version number is displayed on this page. Alternatively, navigate to chrome://settings/help
    Affected if The displayed version number is lower than 142.0.7444.175
  2. Confirm version via command line
    On Windows: Run 'chrome --version' or check 'C:\Program Files\Google\Chrome\Application\chrome.exe' properties. On macOS: Run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' in Terminal. On Linux: Run 'google-chrome --version' or 'google-chrome-stable --version'
    Affected if The reported version is 142.0.7444.174 or earlier
  3. Verify V8 JavaScript engine is in use
    The V8 engine is the default and required JavaScript engine in Chrome. No manual configuration needed. You can verify it is active by opening any webpage and confirming JavaScript executes normally
    Affected if JavaScript executes normally in Chrome (V8 is enabled by default)
  4. Assess exposure to malicious HTML pages
    Check if users have unrestricted web browsing or if browsing is restricted to trusted domains via enterprise policies or parental controls
    Affected if Users can navigate to untrusted or attacker-controlled websites without blocking

You are affected if Chrome version is 142.0.7444.174 or lower and users can access arbitrary web content

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.175 or later
Fixed in 142.0.7444.175
Interim mitigation

Update Google Chrome to version 142.0.7444.175 or later. Organizations should ensure endpoint protection and browser update deployment across all managed devices.

Recommended fix High confidence

Chrome 142.0.7444.175 or later

  1. Open Google Chrome browser
  2. Navigate to Settings > Help > About Google Chrome (or enter chrome://settings/help in the address bar)
  3. Chrome will automatically check for updates
  4. If version 142.0.7444.175 or later is available, click 'Update Google Chrome'
  5. Restart the browser to apply the update
  6. Verify the update by returning to About Google Chrome and confirming the version number

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

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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