Skip to main content
Mallory
CriticalVulnerability

CVE-2026-6768: Mitigation bypass in Firefox Networking: Cookies

Published Apr 21, 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.
CVSS9.8Critical · v3.1
EPSS0.29%21st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Mozilla
IdentifiersCVE-2026-6768CWE-288 · Authentication Bypass Using an…

CVE-2026-6768 is a mitigation bypass vulnerability in Mozilla's Networking: Cookies component affecting Firefox. The issue allows intended security protections in cookie handling or related networking controls to be bypassed. Available information identifies the flaw only at a high level and does not provide public technical detail about the specific vulnerable function or code path. Mozilla corrected the issue in Firefox 150, and the same issue was also referenced in Thunderbird security update coverage.

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 results in a security feature bypass. The associated severity metadata indicates potential for high impact to confidentiality, integrity, and availability, although the precise exploitation chain and downstream effects are not publicly described in the available information. Depending on how the bypass is leveraged, an attacker may be able to circumvent cookie-related protections and use that access to facilitate broader compromise of browser or application security boundaries.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting use of affected versions, restricting access to untrusted web content, and enforcing compensating browser hardening controls where available. Because this is a mitigation bypass in a core browser networking component, no complete workaround is documented in the available information; vendor patching is the primary mitigation.

Remediation

Patch, then assume compromise.

Upgrade affected Mozilla products to vendor-fixed releases, specifically Firefox 150 or later. Where Thunderbird includes the same vulnerable code, apply the corresponding Thunderbird security update released by Mozilla. Standard remediation should prioritize deployment of the vendor security updates referenced in Mozilla advisories.

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-6768 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-6768 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-6768?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-6768.
Is there a patch for CVE-2026-6768?
Upgrade affected Mozilla products to vendor-fixed releases, specifically Firefox 150 or later. Where Thunderbird includes the same vulnerable code, apply the corresponding Thunderbird security update released by Mozilla.
What products are affected by CVE-2026-6768?
Mozilla Firefox and Mozilla Thunderbird.
How severe is CVE-2026-6768?
CVE-2026-6768 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 0.29% (21st percentile) as of Sep 25, 2026.
Activity feed

Recent activity

4 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.