dbcve.org
FirefoxWeb browser · Mozilla

CVE-2025-11710

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 115.29.0 / 140.4.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
A compromised web process using malicious IPC messages could have caused the privileged browser process to reveal blocks of its memory to the compromised process. This vulnerability was fixed in Firefox 144, Firefox ESR 115.29, Firefox ESR 140.4, Thunderbird 144, and Thunderbird 140.4.

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 compromised web process (child process) could send malicious IPC messages to the privileged browser process, tricking it into revealing blocks of its memory back to the compromised process. This constitutes an information disclosure vulnerability where a less-privileged child process can read memory from the more-privileged parent browser process.

MitigationUpdate affected systems to Firefox 144 or later, Firefox ESR 115.29/140.4 or later, or Thunderbird 140.4 or later to remediate this memory disclosure 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
FirefoxWeb browser
Affected:< 115.29.0< 144.0>= 116.0, < 140.4.0
ThunderbirdApplication
Affected:< 140.4.0>= 141.0, < 144.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Identify installed Mozilla product
    Check if Firefox or Thunderbird is installed by looking for the application in the system (e.g., check for firefox or thunderbird executables, or look in typical installation directories like /usr/bin/firefox, C:\Program Files\Mozilla Firefox, or via system package managers)
    Affected if Either Firefox or Thunderbird is installed
  2. Determine Firefox version
    Run 'firefox --version' from command line, or check About Firefox in the application menu, or examine the version file in the installation directory
    Affected if The installed version is < 115.29.0 OR (>= 116.0 AND < 140.4.0) OR (< 144.0 when counting from 115.29.0-115.x range)
  3. Determine Thunderbird version
    Run 'thunderbird --version' from command line, or check About Thunderbird in the application menu, or examine the version file in the installation directory
    Affected if The installed version is < 140.4.0 OR (>= 141.0 AND < 144.0)
  4. Confirm IPC component presence
    The IPC mechanism between web content processes and the privileged browser process is a core component of Firefox/Thunderbird architecture and is always active when the browser runs. This is not a configurable feature.
    Affected if The browser or email client is running with web content process capability (standard operation mode)

A user is affected if they are running any Firefox version before 115.29.0, between 116.0-140.3.x, or before 144.0 in the 115.x-143.x range; or any Thunderbird version before 140.4.0 or between 141.0-143.x, as these versions contain the vulnerable IPC memory leak flaw.

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.29.0 / 140.4.0 / 144.0 or later
Fixed in 115.29.0140.4.0144.0
Interim mitigation

Update affected systems to Firefox 144 or later, Firefox ESR 115.29/140.4 or later, or Thunderbird 140.4 or later to remediate this memory disclosure vulnerability.

Recommended fix High confidence

Firefox 144, Firefox ESR 115.29, Firefox ESR 140.4, Thunderbird 144, or Thunderbird 140.4 (depending on your release channel)

  1. 1. Check current Firefox or Thunderbird version by navigating to Help > About (or using the menu: Firefox > About Firefox / Thunderbird > About Thunderbird)
  2. 2. For Firefox users: If running a version < 115.29.0, upgrade to Firefox ESR 115.29 or later; if running 116.0-140.4.0, upgrade to Firefox 144 or Firefox ESR 140.4
  3. 3. For Thunderbird users: If running a version < 140.4.0, upgrade to Thunderbird 140.4; if running 141.0-144.0, upgrade to Thunderbird 144
  4. 4. Download the appropriate fixed version from the official Mozilla website (www.mozilla.org)
  5. 5. Close all running instances of the application
  6. 6. Install the updated version
  7. 7. Restart the application and verify the version was updated successfully
Caveat Standard major version upgrade - review release notes for any add-on compatibility changes or deprecated features

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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