Skip to main content
Mallory
HighVulnerability

CVE-2026-5732: Integer Overflow in Mozilla Graphics: Text Component

Published Apr 7, 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.
CVSS8.8High · v3.1
EPSS0.36%31st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Mozilla
IdentifiersCVE-2026-5732CWE-190 · Integer Overflow or Wraparound

CVE-2026-5732 is an integer overflow vulnerability in the Graphics: Text component used by Mozilla Firefox and Thunderbird. The issue is attributed to incorrect boundary conditions that can lead to an integer overflow during text-related graphics processing. In affected releases, this flaw may result in memory corruption when specially crafted content is processed. The vulnerability affects Firefox versions earlier than 149.0.2, Firefox ESR versions earlier than 140.9.1, and corresponding Thunderbird releases fixed in 149.0.2 and 140.9.1.

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 can cause memory corruption, potentially leading to application instability or a denial of service through a crash. Available severity information also indicates the flaw may be exploitable for arbitrary code execution in the context of the affected application, with high potential impact to confidentiality, integrity, and availability.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting use of untrusted web or message content in affected clients until updates can be applied. Because the vulnerability requires user interaction, restricting the opening of untrusted pages or email content may reduce risk, but mitigation is incomplete and patching remains necessary.

Remediation

Patch, then assume compromise.

Upgrade affected Mozilla products to fixed versions. Mozilla addressed this vulnerability in Firefox 149.0.2, Firefox ESR 140.9.1, Thunderbird 149.0.2, and Thunderbird 140.9.1. Applying the vendor-provided security updates is the primary remediation.

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-5732 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-5732 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-5732?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-5732.
Is there a patch for CVE-2026-5732?
Upgrade affected Mozilla products to fixed versions. Mozilla addressed this vulnerability in Firefox 149.0.2, Firefox ESR 140.9.1, Thunderbird 149.0.2, and Thunderbird 140.9.1.
What products are affected by CVE-2026-5732?
Mozilla Firefox and Mozilla Thunderbird.
How severe is CVE-2026-5732?
CVE-2026-5732 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.36% (31st percentile) as of Sep 25, 2026.
Activity feed

Recent activity

14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 activity4Community discussion across Reddit, Mastodon, and other social sources.