FirefoxWeb browser · Mozilla

CVE-2026-6763

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-21
Fix available
A fix is available. Upgrade to 140.10.0 / 150.0 or later.
See remediation →
74/100
Remediation priority · Elevated
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
Mitigation bypass in the File Handling 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 · moderate confidence

A mitigation bypass in the File Handling component allows attackers to circumvent existing security controls. This appears to be a vulnerability where a previously mitigated file handling flaw could be re-exploited through a different attack vector.

MitigationUpgrade to Firefox 150+, Firefox ESR 140.10+, Thunderbird 150+, or Thunderbird 140.10+ to obtain the patched version.

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:< 140.10.0< 150.0
ThunderbirdApplication
Affected:>= 140.0, < 140.10.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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

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. Identify installed Mozilla product
    Check if Firefox or Thunderbird is installed. On Windows, look in Program Files. On macOS, check /Applications. On Linux, check package manager or /usr/lib/firefox or /usr/lib/thunderbird.
    Affected if Neither Firefox nor Thunderbird is installed - not affected.
  2. Determine Firefox version
    Open Firefox, go to Menu > Help > About Firefox, or navigate to about:support. The version number is displayed.
    Affected if Version is < 140.10.0 or >= 140.10.0 but < 150.0 - affected.
  3. Determine Thunderbird version
    Open Thunderbird, go to Menu > Help > About Thunderbird, or navigate to about:support. The version number is displayed.
    Affected if Version is >= 140.0 and < 140.10.0 - affected.
  4. Check for Firefox ESR
    If running Firefox ESR, the version format includes ESR (e.g., 140.10esr). Confirm via Menu > Help > About Firefox.
    Affected if Firefox ESR version < 140.10.0 - affected.

The environment is affected if Mozilla Firefox of any type is installed with version below 150.0, or Mozilla Thunderbird is installed with version >= 140.0 but below 140.10.0.

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 140.10.0 / 150.0 or later
Fixed in 140.10.0150.0
Interim mitigation

Upgrade to Firefox 150+, Firefox ESR 140.10+, Thunderbird 150+, or Thunderbird 140.10+ to obtain the patched version.

Recommended fix High confidence

Firefox 150 (or Firefox ESR 140.10); Thunderbird 140.10

  1. 1. Back up your profile data (bookmarks, passwords, emails) before upgrading
  2. 2. Download Firefox 150 (or Firefox ESR 140.10 for enterprise/extended support needs) from the official Mozilla website
  3. 3. Download Thunderbird 140.10 from the official Mozilla website
  4. 4. Close all instances of Firefox and Thunderbird
  5. 5. Install the new version of Firefox by running the downloaded installer
  6. 6. Install the new version of Thunderbird by running the downloaded installer
  7. 7. Restart Firefox and Thunderbird after installation completes
  8. 8. Verify the installed version by checking Help > About Firefox / Thunderbird

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

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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