CVE-2026-92240 is an out-of-bounds read in Mozilla Thunderbird's IMAP response parser. A malicious or compromised IMAP server can send a crafted untagged IMAP ID response, including an untagged '* ID' response, that reaches the vulnerable parsing path before IMAP authentication and causes Thunderbird to read outside the intended buffer bounds. The documented result is a Thunderbird crash.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Pre-authentication out-of-bounds read and denial-of-service vulnerability in Thunderbird's IMAP response parser, triggerable by a malicious or compromised IMAP server.
A vulnerability addressed in the Mozilla Thunderbird update published September 15, 2026; no technical flaw details are provided.
A pre-authentication out-of-bounds-read denial-of-service vulnerability in Thunderbird's IMAP response parser, triggerable by a malicious or compromised IMAP server sending an untagged ID response.
A vulnerability addressed by Mozilla Thunderbird 140.16; no further technical details are provided.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.