CVE-2026-2779
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 · uneditedIncorrect boundary conditions in the Networking: JAR component. This vulnerability was fixed in Firefox 148, Firefox ESR 140.8, Thunderbird 148, and Thunderbird 140.8.
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 · moderate confidenceA memory safety vulnerability exists in Firefox and Thunderbird's Networking/JAR component due to incorrect boundary conditions. This flaw could allow an attacker to trigger out-of-bounds memory access when processing malicious JAR files, potentially leading to remote code execution. The issue affects multiple Mozilla products and was patched in the specified versions.
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.8.0< 148.0< 140.8.0< 148.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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 productsCheck for Firefox or Thunderbird installations: On Windows check Program Files or %LOCALAPPDATA%\Mozilla\Firefox; On Linux check /usr/lib/firefox or /opt; On macOS check /Applications/Firefox.app or /Applications/Thunderbird.app. Also run 'firefox --version' or 'thunderbird --version' from command line.Affected if Either Firefox or Thunderbird is installed on the system
-
Determine Firefox versionRun 'firefox --version' or go to Firefox menu > Help > About Firefox to view the exact version number.Affected if Firefox version is below 140.8.0 or between 141.x and 147.x (any version < 148.0 but not 140.8.0+)
-
Determine Thunderbird versionRun 'thunderbird --version' or go to Thunderbird menu > Help > About Thunderbird to view the exact version number.Affected if Thunderbird version is below 140.8.0 or between 141.x and 147.x (any version < 148.0 but not 140.8.0+)
-
Confirm JAR handling is activeThe JAR/Networking component processes JAR files automatically when Firefox or Thunderbird handles .jar file types or processes archives. This is enabled by default - no user configuration needed. Check if browser is used for general web browsing or email attachments.Affected if The product is used to access web content or process email attachments containing JAR files
You are affected if Firefox or Thunderbird is installed with any version below 140.8.0 or below 148.0, and the software processes web content or email that could include JAR files.
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.8.0148.0
Update affected software to Firefox 148, Firefox ESR 140.8, Thunderbird 148, or Thunderbird 140.8 or later to remediate this vulnerability.
Firefox 148 (or Firefox ESR 140.8) for Firefox users; Thunderbird 148 (or Thunderbird 140.8) for Thunderbird users
- Verify current Firefox or Thunderbird version by navigating to Menu > Help > About (or running firefox --version / thunderbird --version in terminal)
- Download Firefox 148 or Firefox ESR 140.8 from the official Mozilla website (www.mozilla.org)
- Download Thunderbird 148 or Thunderbird 140.8 from the official Mozilla website (www.mozilla.org)
- Close all instances of the application
- Install the downloaded version over the existing installation
- Restart the application
- Verify the installed version matches one of the fixed releases (140.8.0 or 148.0)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2779 — 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-2779 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