CVE-2026-2769
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 Storage: IndexedDB 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 confidenceUse-after-free vulnerability in the Storage: IndexedDB component of Firefox and Thunderbird. This memory safety issue allows freed memory to be accessed, potentially leading to arbitrary code execution or crashes. The vulnerability has a CVSS score of 8.8 (HIGH), indicating significant risk.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 the installed Firefox versionOpen Firefox, go to Help > About Firefox (or navigate to about:support). The version number is displayed at the top.Affected if The version shown is less than 115.33.0, or is 128.0 or higher but less than 140.8.0, or is less than 148.0 (all of these ranges indicate vulnerability).
-
Identify the installed Thunderbird versionOpen Thunderbird, go to Help > About Thunderbird. The version number is displayed.Affected if The version shown is less than 140.8.0 or less than 148.0.
-
Verify IndexedDB is in useIn Firefox, open the Web Developer Tools (F12), go to the Storage tab, and look for IndexedDB entries under the Storage section. Alternatively, visit a site known to use IndexedDB and check if data appears in about:storage.Affected if IndexedDB storage is present and accessible in the browser profile, indicating the vulnerable component is active.
-
Check for browser updatesIn Firefox, go to Help > About Firefox. If an update is available, it will show a button to download and install it. In Thunderbird, check for updates via Help > Check for Updates.Affected if An update is available that would upgrade the version beyond the vulnerable ranges (115.33.0+, 140.8.0+, or 148.0+).
You are affected if you run Firefox version lower than 115.33.0, or 128.0-140.7.x, or lower than 148.0; or Thunderbird version lower than 140.8.0 or lower than 148.0, and IndexedDB storage is in use.
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
Upgrade to Firefox 148, Firefox ESR 115.33, Firefox ESR 140.8, Thunderbird 148, or Thunderbird 140.8 (or later versions) to remediate this vulnerability.
Firefox 148.0 (or Firefox ESR 115.33.0 / Firefox ESR 140.8.0); Thunderbird 148.0 (or Thunderbird 140.8.0)
- 1. Open Firefox or Thunderbird and navigate to the Help menu.
- 2. Select 'About Firefox' or 'About Thunderbird' to check the current version.
- 3. If the version is below 148.0 for Firefox, or below 140.8.0 for Thunderbird (or below 115.33.0 for Firefox ESR 115.x), click 'Check for Updates' or allow automatic updates to complete.
- 4. Restart the application after the update installs.
- 5. Verify the version is now at 148.0 or higher (Firefox), 140.8.0 or higher (Thunderbird), or 115.33.0 or higher (Firefox ESR 115.x).
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-2769 — 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-2769 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