Skip to main content
Mallory
CriticalVulnerability

CVE-2026-92061: Incorrect boundary conditions in Firefox and Thunderbird process sandboxing

Published Sep 15, 2026 · Updated 23 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS0.55%47th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Mozilla
IdentifiersCVE-2026-92061CWE-193

CVE-2026-92061 is an incorrect-boundary-condition vulnerability in the Security: Process Sandboxing component of Mozilla Firefox and Thunderbird, fixed in version 156 of both products. The flaw can weaken process-sandbox boundary enforcement and is associated with limited information disclosure. The affected function, precise boundary-checking error, and technical exploitation mechanism have not been disclosed.

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.

The CVE-specific assessment rates the vulnerability Low, with a CVSS v3.1 score of 3.1, indicating limited confidentiality impact and no integrity or availability impact. A conflicting scanner entry assigns a critical CVSS v3.0 score of 9.8; that higher assessment is not supported by the available technical details. Arbitrary code execution, privilege escalation, and a complete sandbox escape are not established for this CVE.

Mitigation

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

No CVE-specific workaround is documented. Until updates are deployed, restrict use of affected installations for untrusted web content and apply browser and endpoint controls that reduce exposure. These measures reduce exposure but do not correct the boundary-condition flaw.

Remediation

Patch, then assume compromise.

Upgrade affected Firefox and Thunderbird installations to version 156 or a later supported release containing the fix. Earlier versions are identified by version-based detection, but the exact introduction versions are unspecified. Fixes in ESR branches are not established specifically for this CVE.

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-92061 exploited in the wild?
As of Oct 25, 2026, Mallory has no reports of CVE-2026-92061 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-92061?
As of Oct 25, 2026, Mallory has found no public exploit for CVE-2026-92061.
Is there a patch for CVE-2026-92061?
Upgrade affected Firefox and Thunderbird installations to version 156 or a later supported release containing the fix. Earlier versions are identified by version-based detection, but the exact introduction versions are unspecified.
What products are affected by CVE-2026-92061?
Mozilla Firefox and Mozilla Thunderbird.
How severe is CVE-2026-92061?
CVE-2026-92061 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 0.55% (47th percentile) as of Oct 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 activityCommunity discussion across Reddit, Mastodon, and other social sources.