FirefoxWeb browser · Mozilla
CVE-2025-8044
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 · uneditedMemory safety bugs present in Firefox 140 and Thunderbird 140. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability was fixed in Firefox 141 and Thunderbird 141.
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 confidenceMemory safety bugs in Firefox 140 and Thunderbird 140 allowed memory corruption that could potentially be exploited for arbitrary code execution. The vulnerability stems from multiple memory handling issues in the browser and email client components. This was addressed in versions 141 of both products.
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
< 141.0< 141.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Firefox versionRun 'firefox --version' on Linux/macOS, or check the About Firefox dialog (Help > About Firefox) on Windows. On Windows, you can also query the registry key: HKLM\SOFTWARE\Mozilla\Mozilla Firefox\CurrentVersionAffected if The reported version is below 141.0 (e.g., 140.x or earlier)
-
Check installed Thunderbird versionRun 'thunderbird --version' on Linux/macOS, or check the About Thunderbird dialog (Help > About Thunderbird) on Windows. On Windows, you can also query the registry key: HKLM\SOFTWARE\Mozilla\Mozilla Thunderbird\CurrentVersionAffected if The reported version is below 141.0 (e.g., 140.x or earlier)
-
Verify Firefox installation path and version fileOn Linux, check /usr/lib/firefox/ and locate the 'application.ini' or 'firefox' binary. Run: ls -la /usr/lib/firefox/ | head -20 and examine the version from the binary name or contents. On macOS, inspect: /Applications/Firefox.app/Contents/Info.plist for CFBundleShortVersionStringAffected if The version parsed from files or package manager (dpkg -l firefox | grep ii or rpm -q firefox) shows a version below 141.0
Your environment is affected if either Firefox or Thunderbird is installed with a version number lower than 141.0, as the memory corruption vulnerability exists in all prior versions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped141.0
Upgrade to Firefox 141 or Thunderbird 141 to remediate this vulnerability. Organizations should deploy the updated versions across all affected endpoints.
Firefox 141.0 and Thunderbird 141.0
- Upgrade Firefox to version 141.0 or later
- Upgrade Thunderbird to version 141.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-8044 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-8044 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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