ChromeWeb browser · Google

CVE-2025-6555

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-24
Fix available
A fix is available. Upgrade to 138.0.7204.49 or later.
See remediation →
61/100
Remediation priority · Elevated
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
Use after free in Animation in Google Chrome prior to 138.0.7204.49 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 · moderate confidence

A use-after-free vulnerability exists in Google Chrome's Animation component prior to version 138.0.7204.49. The vulnerability occurs when memory for an animation object is freed but a pointer to that memory remains active, leading to heap corruption when the dangling pointer is dereferenced. A remote attacker can trigger this via a specially crafted HTML page.

MitigationUpgrade Google Chrome to version 138.0.7204.49 or later to remediate this vulnerability.

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

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

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. Check if Google Chrome is installed
    Locate the Chrome executable. On Windows, check C:\Program Files\Google\Chrome\Application\chrome.exe. On macOS, check /Applications/Google Chrome.app. On Linux, check /usr/bin/google-chrome or /opt/google/chrome/google-chrome.
    Affected if Google Chrome browser is present on the system
  2. Determine the installed Chrome version
    Open chrome://settings/help in the Chrome browser, or run 'google-chrome --version' in terminal on Linux/macOS. On Windows, you can also right-click chrome.exe and view Properties > Details > File version.
    Affected if The displayed version number is lower than 138.0.7204.49 or the command returns a version older than 138.0.7204.49
  3. Verify the Animation component is in use
    This is a built-in Chrome component used for web animations. No user configuration is required. The vulnerability triggers when Chrome renders a specially crafted HTML page with specific animation sequences.
    Affected if Chrome is used to browse untrusted web content (the attack requires viewing a malicious HTML page)

The user is affected if Google Chrome is installed and its version is lower than 138.0.7204.49, and the browser has been used to view 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 138.0.7204.49 or later
Fixed in 138.0.7204.49
Interim mitigation

Upgrade Google Chrome to version 138.0.7204.49 or later to remediate this vulnerability.

Recommended fix High confidence

Chrome 138.0.7204.49 or later

  1. Open Google Chrome on your system
  2. Click the three-dot menu icon in the top-right corner of the browser window
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. Chrome will automatically check for updates and display the current version
  6. If an update is available, click 'Update Google Chrome' and restart the browser
  7. After restart, return to 'About Google Chrome' and verify the version number is 138.0.7204.49 or later

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-6555 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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