dbcve.org
ChromeWeb browser · Google

CVE-2025-13720

HIGH · 8.8 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 →
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
Bad cast in Loader in Google Chrome prior to 143.0.7499.41 allowed a remote attacker who had compromised the renderer process 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 bad cast vulnerability in Google Chrome's Loader component allows a remote attacker who has already compromised the renderer process to potentially exploit heap corruption via a crafted HTML page. The vulnerability stems from improper type handling during the casting operation, which can lead to memory corruption and potential code execution.

MitigationUpdate Google Chrome to version 143.0.7499.41 or later. In enterprise environments, ensure automated patch management systems deploy the latest Chrome version across all affected 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:< 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
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. Verify Chrome is installed
    Check for Chrome executable at typical install paths: Windows: C:\Program Files\Google\Chrome\Application\chrome.exe, macOS: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome, Linux: /usr/bin/google-chrome or /usr/bin/chrome
    Affected if Chrome is not installed on the system
  2. Determine installed Chrome version
    Open chrome://version in the Chrome browser, or run 'google-chrome --version' (Linux) / 'chrome --version' (Windows) / '/Applications/Google\ Chrome --version' (macOS) from command line, or check the version property of the Chrome executable
    Affected if Cannot determine version or Chrome is not found
  3. Compare version to affected range
    Compare your installed version number to the vulnerable versions: 143.0.7499.40 and earlier, or 143.0.7499.41 and earlier
    Affected if Installed version is less than 143.0.7499.40 or less than 143.0.7499.41 (note: two version ranges are provided, treat either as vulnerable)
  4. Assess renderer compromise risk
    Review system for indicators of compromise or consider whether untrusted web content is processed by Chrome; the vulnerability requires an already-compromised renderer process to be exploitable
    Affected if User regularly visits untrusted websites or system shows signs of malware/compromise

System is affected if Google Chrome is installed with a version prior to 143.0.7499.40 or 143.0.7499.41, and the attacker could potentially compromise the renderer process through malicious 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 143.0.7499.40 / 143.0.7499.41 or later
Fixed in 143.0.7499.40143.0.7499.41
Interim mitigation

Update Google Chrome to version 143.0.7499.41 or later. In enterprise environments, ensure automated patch management systems deploy the latest Chrome version across all affected endpoints.

Recommended fix High confidence

Chrome 143.0.7499.41 or later

  1. Open Google Chrome
  2. Navigate to Settings > Help > About Google Chrome
  3. Chrome will automatically check for updates
  4. If an update is available to version 143.0.7499.41 or later, click 'Update Google Chrome'
  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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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