CVE-2025-5986
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 · uneditedA crafted HTML email using mailbox:/// links can trigger automatic, unsolicited downloads of .pdf files to the user's desktop or home directory without prompting, even if auto-saving is disabled. This behavior can be abused to fill the disk with garbage data (e.g. using /dev/urandom on Linux) or to leak Windows credentials via SMB links when the email is viewed in HTML mode. While user interaction is required to download the .pdf file, visual obfuscation can conceal the download trigger. Viewing the email in HTML mode is enough to load external content. This vulnerability was fixed in Thunderbird 128.11.1 and Thunderbird 139.0.2.
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 confidenceThunderbird fails to properly restrict mailbox:/// links in HTML emails, allowing crafted messages to trigger automatic, unsolicited PDF downloads to the user's desktop or home directory even when auto-saving is disabled. This can be exploited for disk space exhaustion or Windows credential leakage via SMB links.
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< 128.11.1>= 135.0, < 139.0.2CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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.
-
Verify Thunderbird versionIn Thunderbird, go to Help > About Thunderbird (or Thunderbird > About Thunderbird on macOS) to see the installed version numberAffected if The installed version is before 128.11.1, or is 135.0 through 139.0.1 (the version falls within < 128.11.1 OR >= 135.0 AND < 139.0.2)
-
Confirm HTML email rendering is enabledGo to Settings (or Preferences) > Privacy & Security > Display external content in messages - check if this option is enabledAffected if HTML email rendering or external content loading is enabled (this is the attack surface for the mailbox:/// link vulnerability)
-
Check email account settings for content handlingRight-click on each email account > Settings > Display > ensure 'Render HTML messages' is set to 'As plain text' or verify that 'Allow remote content in messages' is disabledAffected if HTML message rendering is set to render as HTML rather than plain text, and remote content is allowed
A user is affected if their Thunderbird version falls in the ranges < 128.11.1 OR >= 135.0 to < 139.0.2 AND they have HTML email rendering or external content loading enabled, as this allows the mailbox:/// link attack vector to execute.
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 · scoped128.11.1139.0.2
Update Thunderbird to version 128.11.1 or 139.0.2 or later. Consider disabling HTML email rendering or external content loading as a defense-in-depth measure.
Thunderbird 128.11.1 (older branch) or Thunderbird 139.0.2 (newer branch)
- Check your current Thunderbird version by clicking Help > About Thunderbird
- If your version is < 128.11.1 (older branch), upgrade to version 128.11.1 or later
- If your version is >= 135.0 but < 139.0.2 (newer branch), upgrade to version 139.0.2 or later
- Download the latest Thunderbird from the official Mozilla website (www.mozilla.org) or use your system's package manager to update
- Restart Thunderbird after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5986 — 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-5986 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