CVE-2026-6785 is a bundled Mozilla vulnerability covering more than 150 memory safety defects in Firefox, Firefox ESR, Thunderbird, and Thunderbird ESR. The affected releases are Firefox 149, Firefox ESR 115.34, Firefox ESR 140.9, Thunderbird 149, and Thunderbird ESR 140.9. The flaws are in Gecko-rendered content handling and include multiple classes of memory safety weakness, notably use-after-free, out-of-bounds read, and out-of-bounds write conditions. Mozilla stated that some of the bugs showed evidence of memory corruption and that, with sufficient effort, some could be exploited to run arbitrary code. Because this CVE aggregates several underlying defects rather than a single root cause or function, no single vulnerable function can be identified from the available information.
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.
22 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity batch Mozilla vulnerability covering over 150 memory safety bugs in the shared Gecko engine across Firefox and Thunderbird product lines, with potential for arbitrary code execution.
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.
A specific CVE identifier mentioned as an example in a discussion about duplicate or repeated CVE-related records in Linux kernel and vulnerability databases; no technical details of the flaw itself 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.