Skip to main content
Mallory
HighVulnerability

CVE-2026-12326: Memory safety bugs in Firefox 151 and Thunderbird 151

Published Jun 16, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS0.36%31st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Mozilla
IdentifiersCVE-2026-12326CWE-119 · Improper Restriction of Operations…

CVE-2026-12326 covers multiple memory safety bugs affecting Firefox 151 and Thunderbird 151. Mozilla states that some of these bugs showed evidence of memory corruption and assessed that, with sufficient effort, some could potentially be exploited to run arbitrary code. The provided content does not identify a single vulnerable function or subsystem for this CVE; instead, it describes a grouped set of memory safety defects fixed in Firefox 152 and Thunderbird 152.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation could cause memory corruption and may enable arbitrary code execution in the context of the affected application. As this is a browser/mail client memory safety issue, exploitation would typically be triggered by attacker-controlled content processed by Firefox or Thunderbird. The broader advisory context indicates that memory corruption flaws in Firefox can also be chained with other vulnerabilities, such as sandbox escape bugs, to increase impact up to compromise of the underlying system, but that chaining is not specifically attributed to this CVE alone.

Mitigation

If you can’t patch tonight, do this now.

No specific vendor workaround or temporary mitigation is provided in the supplied content. The primary mitigation is prompt patching to Firefox 152 and Thunderbird 152 or later. Until updates are fully deployed, reduce exposure by limiting access to untrusted web content and attachments, enforcing least privilege, and using exploit-mitigation and endpoint protection controls, though these are general risk-reduction measures rather than CVE-specific fixes.

Remediation

Patch, then assume compromise.

Upgrade affected products to fixed versions released by Mozilla. The provided content states that CVE-2026-12326 was fixed in Firefox 152 and Thunderbird 152. Advisory context also indicates Mozilla released corresponding ESR updates alongside Firefox 152; however, the specific ESR mapping for this CVE is not explicitly stated in the CVE description provided here.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
MozillaFirefoxapplication
MozillaThunderbirdapplication
FAQ

Frequently asked questions

Is CVE-2026-12326 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-12326 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-12326?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-12326.
Is there a patch for CVE-2026-12326?
Upgrade affected products to fixed versions released by Mozilla. The provided content states that CVE-2026-12326 was fixed in Firefox 152 and Thunderbird 152.
What products are affected by CVE-2026-12326?
Mozilla Firefox and Mozilla Thunderbird.
How severe is CVE-2026-12326?
CVE-2026-12326 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.36% (31st percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.