FirefoxWeb browser · Mozilla

CVE-2026-2797

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-24
Fix available
A fix is available. Upgrade to 148.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Use-after-free in the JavaScript: GC component. This vulnerability was fixed in Firefox 148 and Thunderbird 148.

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 confidence

A use-after-free vulnerability exists in the JavaScript garbage collection (GC) component of Firefox and Thunderbird. This memory safety flaw allows an attacker to potentially execute arbitrary code or cause denial of service by accessing freed memory. The vulnerability was addressed in Firefox 148 and Thunderbird 148.

MitigationUpdate Firefox and Thunderbird to version 148 or later through the application's built-in update mechanism or by downloading the latest version from the official Mozilla website.

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
FirefoxWeb browser
Affected:< 148.0
ThunderbirdApplication
Affected:< 148.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Firefox is installed and get its version
    Open Firefox, go to Help > About Firefox, or run 'firefox --version' in terminal. On Windows, check Add/Remove Programs or the executable properties. On Linux, check your package manager: dpkg -l | grep firefox or rpm -qa | grep firefox.
    Affected if Firefox version is less than 148.0
  2. Check if Thunderbird is installed and get its version
    Open Thunderbird, go to Help > About Thunderbird, or run 'thunderbird --version' in terminal. On Windows, check Add/Remove Programs. On Linux, check your package manager: dpkg -l | grep thunderbird or rpm -qa | grep thunderbird.
    Affected if Thunderbird version is less than 148.0
  3. Compare installed versions against affected range
    Review the version numbers obtained from the previous checks. The affected version range is any version prior to 148.0 (for example, 147.x, 147.0.1, 146.x, etc.).
    Affected if Either Firefox or Thunderbird is installed with a version number lower than 148.0

You are affected if either Mozilla Firefox or Thunderbird is installed with a version lower than 148.0, as this is a core JavaScript GC component flaw present in all earlier versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 148.0 or later
Fixed in 148.0
Interim mitigation

Update Firefox and Thunderbird to version 148 or later through the application's built-in update mechanism or by downloading the latest version from the official Mozilla website.

Recommended fix High confidence

Firefox 148.0 / Thunderbird 148.0

  1. 1. Back up any important data and bookmarks
  2. 2. Open Firefox or Thunderbird
  3. 3. Navigate to Help > About Firefox (or About Thunderbird)
  4. 4. Click 'Check for Updates' or allow the automatic check to complete
  5. 5. If version 148.0 or later is available, download and install it
  6. 6. Restart the application after the update completes
  7. 7. Alternatively, download Firefox 148.0 or Thunderbird 148.0 directly from the official Mozilla website (www.mozilla.org) and install over the current version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2797 — 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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2797 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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