FirefoxWeb browser · Mozilla

CVE-2025-13014

HIGH · 8.8 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 115.30.0 / 140.5.0 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 the Audio/Video component. This vulnerability was fixed in Firefox 145, Firefox ESR 140.5, Firefox ESR 115.30, Thunderbird 145, and Thunderbird 140.5.

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 use-after-free vulnerability in the Audio/Video component of Firefox and Thunderbird allows memory corruption that could potentially be exploited for arbitrary code execution. The vulnerability is fixed in the listed patched versions.

MitigationUpgrade affected systems to Firefox 145, Firefox ESR 140.5/115.30, or Thunderbird 145/140.5 as appropriate for the deployment.

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
FirefoxWeb browser
Affected:< 115.30.0< 145.0>= 140.0, < 140.5.0

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 Firefox version
    Open Firefox, click the menu button (three horizontal lines), select Help, then About Firefox. The version number will be displayed.
    Affected if The version is less than 115.30.0, OR between 140.0 and 140.5.0 (inclusive of 140.0, exclusive of 140.5.0), OR less than 145.0 if not covered by the previous ranges
  2. Check installed Thunderbird version
    Open Thunderbird, click the menu button (three horizontal lines), select Help, then About Thunderbird. The version number will be displayed.
    Affected if The version is less than 115.30.0, OR between 140.0 and 140.5.0 (inclusive of 140.0, exclusive of 140.5.0), OR less than 145.0 if not covered by the previous ranges
  3. Confirm Audio/Video component usage
    This vulnerability affects the Audio/Video component. Check if the browser has been used for playing media (HTML5 video, WebRTC, media APIs). This is typically automatic in modern web browsing.
    Affected if The browser or Thunderbird has been used to play any audio or video content, which loads the affected component

You are affected if your Firefox version is below 115.30.0, between 140.0-140.4.x, or below 145.0 (for non-ESR versions not covered by those ranges), or your Thunderbird version falls into the same vulnerable ranges.

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 115.30.0 / 140.5.0 / 145.0 or later
Fixed in 115.30.0140.5.0145.0
Interim mitigation

Upgrade affected systems to Firefox 145, Firefox ESR 140.5/115.30, or Thunderbird 145/140.5 as appropriate for the deployment.

Recommended fix High confidence

Firefox 145.0 or later; or Firefox ESR 115.30.0 / Firefox ESR 140.5.0 for enterprise ESR users

  1. Close all Firefox windows completely before updating
  2. Open Firefox and navigate to Help > About Firefox
  3. Click 'Check for Updates' to trigger the built-in update mechanism
  4. Download and install the available update when prompted
  5. Restart Firefox after the update completes
  6. Verify the installed version by checking Help > About Firefox - it should show 145.0 or later (or 115.30.0 for ESR)
Caveat Standard Firefox minor updates typically have low risk; major version jumps may occasionally affect legacy extensions or settings

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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