CVE-2026-113868 Mozilla CVE debrief

Who should care

Thunderbird administrators and users should assess exposure and prioritize verification and remediation. This includes reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. They should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Why it matters

Thunderbird users should assess exposure and prioritize verification and remediation due to a vulnerability in NTLM authentication.

• Potential uninitialized memory disclosure to servers
• Possible crashes due to out-of-bounds read
• Verification of affected systems and patching required
• Potential impact on NTLM authentication usage

Technical summary

The vulnerability occurs in Thunderbird's NTLM authentication for POP3 and SMTP. A malicious server could send a challenge causing Thunderbird to include uninitialized heap memory in its NTLM response, disclosing that memory to the server. A challenge consisting only of base64 padding also caused an out-of-bounds read, crashing Thunderbird. This affected accounts configured to use NTLM or GSSAPI authentication.

Defensive priority

Defenders should prioritize patching affected Thunderbird installations to prevent potential memory disclosure and crashes.

Recommended defensive actions

• Verify and apply patches for affected Thunderbird installations
• Assess exposure of Thunderbird installations to NTLM authentication
• Monitor for potential crashes and memory disclosure
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, affected versions, and fixed versions. However, the CVSS score and severity are not provided. The vulnerability was fixed in Thunderbird 158.0.1 and Thunderbird 153.5.1. There is no information on whether the vulnerability is being actively exploited. Defenders should verify affected systems and apply patches. The CVE record was published on 2026-10-20T19:14:55.520Z and has not been modified since then.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.