CVE-2026-2770
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 DOM: Bindings (WebIDL) component. This vulnerability was fixed in Firefox 148, Firefox ESR 115.33, 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 · high confidenceA use-after-free vulnerability exists in the DOM Bindings (WebIDL) component of Firefox and Thunderbird. This memory corruption flaw allows an attacker to potentially execute arbitrary code by manipulating object lifecycle in the WebIDL bindings layer.
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< 115.33.0< 148.0>= 128.0, < 140.8.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.
-
Check if Firefox is installedOn Windows: look for Firefox in Program Files or check the registry at HKLM\SOFTWARE\Mozilla\Mozilla Firefox\CurrentVersion. On Linux: run 'which firefox' or check /usr/lib/firefox. On macOS: check /Applications/Firefox.appAffected if Firefox is present on the system
-
Check if Thunderbird is installedOn Windows: look for Thunderbird in Program Files or check the registry at HKLM\SOFTWARE\Mozilla\Thunderbird\CurrentVersion. On Linux: run 'which thunderbird' or check /usr/lib/thunderbird. On macOS: check /Applications/Thunderbird.appAffected if Thunderbird is present on the system
-
Determine Firefox versionRun 'firefox --version' from command line, or on Windows open Help > About Firefox, or read the version from the registry key HKLM\SOFTWARE\Mozilla\Mozilla Firefox\CurrentVersionAffected if The installed version is < 115.33.0, OR >= 128.0 AND < 140.8.0, OR >= 148.0 but < 148.0 (check against all ranges)
-
Determine Thunderbird versionRun 'thunderbird --version' from command line, or on Windows open Help > About Thunderbird, or read the version from the registry key HKLM\SOFTWARE\Mozilla\Thunderbird\CurrentVersionAffected if The installed version is < 140.8.0 OR < 148.0 (check against all ranges)
You are affected if Firefox is installed with a version less than 115.33.0, or between 128.0 and 140.8.0 exclusive, or less than 148.0; OR if Thunderbird is installed with a version less than 140.8.0 or less than 148.0.
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 · scoped115.33.0140.8.0148.0
Update affected installations to Firefox 148, Firefox ESR 115.33/140.8, or Thunderbird 148/140.8 or later to remediate this critical vulnerability.
Firefox 148, Firefox ESR 115.33, Firefox ESR 140.8, Thunderbird 140.8, or Thunderbird 148 (depending on your release channel)
- Check current Firefox or Thunderbird version via Help > About (or running 'firefox --version' / 'thunderbird --version' in terminal)
- For Firefox: Navigate to https://www.mozilla.org/firefox/all/ and download version 148 (or ESR 115.33 or ESR 140.8 depending on your release channel needs)
- For Thunderbird: Navigate to https://www.thunderbird.net/ and download version 140.8 or 148
- Close all Firefox/Thunderbird instances
- Run the installer and follow the prompts to complete the upgrade
- Restart the application and verify the version matches the expected fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2770 — 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 sources- www.mozilla.org
- www.mozilla.org
- www.mozilla.org
- www.mozilla.org
- www.mozilla.org
- bugzilla.mozilla.org
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- bugzilla.redhat.com
- security.access.redhat.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2770 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