CVE-2026-6786 is an aggregate Mozilla vulnerability covering more than 100 memory-safety defects affecting Firefox 149 and earlier, Firefox ESR 140.9 and earlier, Thunderbird 149 and earlier, and Thunderbird ESR 140.9 and earlier. The bundled flaws include memory-corruption conditions such as use-after-free, out-of-bounds read, and out-of-bounds write issues in shared browser components including Gecko and SpiderMonkey. Mozilla stated that some of the underlying bugs showed evidence of memory corruption and could, with sufficient exploitation effort, be developed into arbitrary code execution. Because Firefox and Thunderbird share core rendering and scripting components, the issue spans both product lines, although standard Thunderbird email viewing is generally less exposed because scripting is disabled by default.
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.
23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A memory safety vulnerability affecting Firefox and Thunderbird releases, involving bugs with evidence of memory corruption that could potentially be exploited for arbitrary code execution.
An aggregate Mozilla memory safety vulnerability covering over 100 underlying bugs in Firefox and Thunderbird that could plausibly enable remote code execution if left unpatched.
A specific vulnerability identifier mentioned as one of the security issues addressed in Firefox 150, but no technical details are provided in the content.
A specific Firefox vulnerability mentioned only as an example in statistics about CVE references; no 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.