Skip to main content
Mallory
HighVulnerability

CVE-2026-5733: Incorrect boundary conditions in Firefox WebGPU

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.32%25th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Mozilla
IdentifiersCVE-2026-5733CWE-119 · Improper Restriction of Operations…

CVE-2026-5733 is an incorrect boundary conditions vulnerability in the Graphics: WebGPU component of Mozilla Firefox and Mozilla Thunderbird. The flaw affects Firefox versions earlier than 149.0.2 and was fixed in Firefox 149.0.2 and Thunderbird 149.0.2. The available information indicates improper bounds handling within WebGPU processing, creating a memory-safety condition consistent with CWE-119. Mozilla-associated severity metadata indicates the issue may be exploitable in a browser context with user interaction.

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 may lead to severe compromise of confidentiality, integrity, and availability. Available vendor-associated context indicates that exploitation of vulnerabilities addressed in the same Thunderbird security update could enable remote code execution or denial of service, and the CVSS vector assigned to this CVE reflects high impact across 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 content and disabling or restricting access to WebGPU functionality where operationally feasible until patched versions can be deployed. Prioritize rapid rollout of the vendor update because no specific workaround is documented in the available information.

Remediation

Patch, then assume compromise.

Upgrade affected Mozilla products to fixed releases. Firefox should be updated to version 149.0.2 or later, and Thunderbird should be updated to version 149.0.2 or later where applicable. Applying the vendor security update is the primary remediation.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
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-5733 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-5733 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-5733?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-5733.
Is there a patch for CVE-2026-5733?
Upgrade affected Mozilla products to fixed releases. Firefox should be updated to version 149.0.2 or later, and Thunderbird should be updated to version 149.0.2 or later where applicable.
What products are affected by CVE-2026-5733?
Mozilla Firefox and Mozilla Thunderbird.
How severe is CVE-2026-5733?
CVE-2026-5733 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.32% (25th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

3 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 activity1Community discussion across Reddit, Mastodon, and other social sources.