CVE-2026-6759
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUse-after-free in the Widget: Cocoa component. This vulnerability was fixed in Firefox 150, Firefox ESR 140.10, Thunderbird 150, and Thunderbird 140.10.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA use-after-free vulnerability exists in the Widget: Cocoa component of Firefox and Thunderbird. This occurs when the program continues to reference memory after it has been freed, potentially allowing remote attackers to cause denial of service or execute arbitrary code via crafted web content. The vulnerability affects macOS builds using the Cocoa UI framework.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 140.10.0< 150.0>= 140.0, < 140.10.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Mozilla productRun 'firefox --version' or check /Applications/Firebird.app or /Applications/Thunderbird.app, or check Help > About in the applicationAffected if Product is Firefox or Thunderbird on macOS
-
Check operating systemRun 'uname -s' or check System Preferences > About > System Report to confirm macOSAffected if Running macOS (the vulnerability only affects macOS builds using Cocoa UI framework)
-
Determine installed Firefox versionRun 'firefox --version' or check Firefox > Help > About Firefox. Compare the version number to the affected ranges: < 140.10.0 or < 150.0Affected if Firefox version is 139.x, 140.0-140.9.x, or any version below 140.10.0 (for ESR) or 150.0 (for standard)
-
Determine installed Thunderbird versionRun 'thunderbird --version' or check Thunderbird > Help > About Thunderbird. Compare the version number to the affected range: >= 140.0 and < 140.10.0Affected if Thunderbird version is 140.0 through 140.9.x (140.10.0 and later are fixed)
-
Verify Cocoa UI framework is in useThis is automatic on macOS Firefox/Thunderbird - the Widget: Cocoa component is used by default on macOS buildsAffected if Running the affected product on macOS means the Cocoa UI framework is active and the vulnerability applies
Affected if running Firefox < 140.10.0 or < 150.0, or Thunderbird 140.0-140.9.x, on macOS with the default Cocoa UI framework.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped140.10.0150.0
Update affected installations to Firefox 150, Firefox ESR 140.10, Thunderbird 150, or Thunderbird 140.10 or later. Organizations should verify deployment of patched versions across all endpoints.
Firefox 150 (or Firefox ESR 140.10), Thunderbird 140.10 (or Thunderbird 150)
- 1. Check the current installed version of Firefox or Thunderbird by navigating to the application and selecting Help > About Firefox/Thunderbird.
- 2. For Firefox users: If currently on version 140.x ESR, upgrade to Firefox ESR 140.10 or later. If on version 149 or earlier (non-ESR), upgrade to Firefox 150 or later.
- 3. For Thunderbird users: If on version 140.x, upgrade to Thunderbird 140.10 or later. If on an earlier version, upgrade to Thunderbird 150 or later.
- 4. Download the latest version from the official Mozilla website at https://www.mozilla.org/ or use the application's built-in update mechanism (Help > Check for Updates).
- 5. Install the updated version and restart the application.
- 6. Verify the fix by checking the version again (Help > About) to confirm the installed version matches or exceeds the fixed release.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6759 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6759 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data