CVE-2025-0238
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 · uneditedAssuming a controlled failed memory allocation, an attacker could have caused a use-after-free, leading to a potentially exploitable crash. This vulnerability was fixed in Firefox 134, Firefox ESR 128.6, Firefox ESR 115.19, Thunderbird 134, and Thunderbird 128.6.
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 confidenceA use-after-free vulnerability in Firefox and Thunderbird where an attacker can trigger a controlled failed memory allocation, causing the application to use memory that has already been freed. This can lead to a potentially exploitable crash.
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< 115.19.0< 134.0>= 116.0, < 128.6.0< 128.6>= 129.0, < 134.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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Firefox version on WindowsOpen Firefox, click Help > About Firefox, or go to about:support in the address bar. The version number is displayed at the top of the page.Affected if The version shown is earlier than 115.19.0, or earlier than 128.6.0 (for versions 116.0-127.x), or earlier than 134.0 (for versions 128.0-133.x).
-
Check installed Firefox version on macOSOpen Firefox, click Firefox from the menu bar, then select About Firefox. The version number appears in the dialog.Affected if The version shown is earlier than 115.19.0, or earlier than 128.6.0 (for versions 116.0-127.x), or earlier than 134.0 (for versions 128.0-133.x).
-
Check installed Firefox version on LinuxOpen a terminal and run: firefox --versionAffected if The version output is earlier than 115.19.0, or earlier than 128.6.0 (for versions 116.0-127.x), or earlier than 134.0 (for versions 128.0-133.x).
-
Check installed Thunderbird version on WindowsOpen Thunderbird, click Help > About Thunderbird. The version number is displayed in the dialog.Affected if The version shown is earlier than 128.6 (for versions 129.0-133.x), or earlier than 134.0 (for versions earlier than 129.0).
-
Check installed Thunderbird version on macOS or LinuxOn macOS: Open Thunderbird, click Thunderbird from menu, select About Thunderbird. On Linux: Open terminal and run: thunderbird --versionAffected if The version shown is earlier than 128.6 (for versions 129.0-133.x), or earlier than 134.0 (for versions earlier than 129.0).
Your environment is affected if any installed Firefox version is below 115.19.0, below 128.6.0 (for 116.0-127.x range), or below 134.0 (for 128.0-133.x range), OR any installed Thunderbird version is below 128.6 (for 129.0-133.x range) or below 134.0 (for versions before 129.0).
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 · scoped115.19.0128.6128.6.0
Update to Firefox 134, Firefox ESR 128.6/115.19, Thunderbird 134/128.6 or later to remediate this vulnerability.
Firefox 134.0 / Firefox ESR 128.6.0 / Firefox ESR 115.19.0 / Thunderbird 134.0 / Thunderbird 128.6.0
- Check current Firefox or Thunderbird version via Help > About (or running 'firefox --version' / 'thunderbird --version' in terminal)
- For Firefox stable users: upgrade to Firefox 134.0 or later
- For Firefox ESR users: upgrade to Firefox ESR 128.6.0 or later (or Firefox ESR 115.19.0 or later for older ESR line)
- For Thunderbird users: upgrade to Thunderbird 128.6.0 or later (or Thunderbird 134.0 for stable line)
- Download from official Mozilla releases at https://www.mozilla.org/ or use system package manager
- Restart the application after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0238 — 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-0238 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