dbcve.org
ChromeWeb browser · Google

CVE-2025-13721

HIGH · 7.5 CVSS v3.1 Published 2025-12-02
Fix available
A fix is available. Upgrade to 143.0.7499.40 / 143.0.7499.41 or later.
See remediation →
82/100
Remediation priority · High
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 143.0.7499.41 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)

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 vulnerability in Google Chrome's V8 JavaScript engine (prior to version 143.0.7499.41) allows remote attackers to corrupt heap memory via a specially crafted HTML page. The race condition occurs during concurrent JavaScript execution in the V8 engine, leading to memory corruption that can be exploited for code execution.

MitigationUpgrade Google Chrome to version 143.0.7499.41 or later. In enterprise environments, deploy the update via standard patch management infrastructure (e.g., SCCM, Group Policy, Intune).

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.40< 143.0.7499.41

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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
    Check for chrome.exe in typical installation paths: %ProgramFiles%\Google\Chrome\Application\chrome.exe, %LocalAppData%\Google\Chrome\Application\chrome.exe, or run 'Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\chrome.exe" -ErrorAction SilentlyContinue'
    Affected if Chrome executable is found on the system
  2. Retrieve installed Chrome version
    Open Chrome, navigate to chrome://settings/help, or run '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' or '"C:\Program Files\Google\Chrome\Application\chrome.exe" --product-version' from Command Prompt or PowerShell
    Affected if Version number is displayed and is lower than 143.0.7499.41
  3. Confirm V8 JavaScript engine is in use
    The V8 engine is embedded in Chrome and processes all JavaScript; no separate check needed - this is always true when Chrome is running JavaScript content
    Affected if Chrome processes any JavaScript-enabled web content (which is the default behavior)
  4. Check for concurrent JavaScript execution scenarios
    Review browser usage for pages with concurrent/parallel JavaScript operations (Web Workers, SharedArrayBuffer, parallel fetch promises, async iterators) - inspect open tabs or recently visited sites using Chrome DevTools Performance tab
    Affected if User visits or interacts with web pages that execute concurrent JavaScript operations

A user is affected if Google Chrome version is lower than 143.0.7499.41 and the browser is used to render web pages with JavaScript content, particularly pages leveraging concurrent JavaScript features.

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.40 / 143.0.7499.41 or later
Fixed in 143.0.7499.40143.0.7499.41
Interim mitigation

Upgrade Google Chrome to version 143.0.7499.41 or later. In enterprise environments, deploy the update via standard patch management infrastructure (e.g., SCCM, Group Policy, Intune).

Recommended fix High confidence

Chrome 143.0.7499.41 or later

  1. Open Google Chrome
  2. Navigate to Help > About Google Chrome
  3. Chrome will check for updates and automatically download version 143.0.7499.41 or later
  4. Click 'Update Google Chrome' if prompted
  5. Restart the browser to complete the update

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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