dbcve.org
ChromeWeb browser · Google

CVE-2025-13638

HIGH · 8.8 CVSS v3.1 Published 2025-12-02
Fix available
A fix is available. Upgrade to 143.0.7499.40 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
Use after free in Media Stream 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: Low)

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

Use-after-free vulnerability in Chrome's Media Stream component allows a remote attacker to exploit heap corruption via a malicious HTML page. The vulnerability exists in versions prior to 143.0.7499.41 and can lead to code execution or denial of service.

MitigationUpdate Google Chrome to version 143.0.7499.41 or later. For enterprise environments, deploy the update via standard patch management processes and verify compatibility with internal applications using media streams.

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

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. Check installed Google Chrome version
    Navigate to chrome://settings/help in the Chrome browser, or look at 'About Google Chrome' in the Chrome menu. The version number is displayed on that page.
    Affected if The displayed version is less than 143.0.7499.40 (for example, 143.0.7499.39, 142.x.x.x, or earlier)
  2. Verify Media Stream component is present
    The Media Stream component is part of Chrome's core media handling. There is no separate enable/disable toggle - it is built into Chrome. The presence of getUserMedia API support can be verified by opening chrome://flags and searching for WebRTC or media-related flags.
    Affected if The Media Stream component exists in the installed Chrome version (this is true for all standard Chrome installations)
  3. Confirm Chrome is used for media handling
    Check if the browser is used for web applications that access camera/microphone (video conferencing, recording apps, etc.). No specific configuration check is needed as the vulnerability triggers upon visiting a malicious page with media functionality.
    Affected if Users access web pages that utilize Media Stream API (getUserMedia, MediaRecorder, or WebRTC) - which includes many common video call and recording web apps

The environment is affected if Google Chrome version is lower than 143.0.7499.40 AND the browser is used to access web content, since the use-after-free in the Media Stream component triggers upon visiting a malicious HTML page.

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 or later
Fixed in 143.0.7499.40
Interim mitigation

Update Google Chrome to version 143.0.7499.41 or later. For enterprise environments, deploy the update via standard patch management processes and verify compatibility with internal applications using media streams.

Recommended fix High confidence

Chrome 143.0.7499.41

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. Chrome will automatically check for updates
  3. If an update is available, click 'Update Google Chrome'
  4. Restart Chrome to complete the update
  5. Verify the version by navigating to chrome://settings/help and confirming the version is 143.0.7499.41 or later

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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