dbcve.org
FirefoxWeb browser · Mozilla

CVE-2026-6773

HIGH · 7.5 CVSS v3.1 Published 2026-04-21
Fix available
A fix is available. Upgrade to 150.0 or later.
See remediation →
84/100
Remediation priority · High
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
Denial-of-service due to integer overflow in the Graphics: WebGPU component. This vulnerability was fixed in Firefox 150 and Thunderbird 150.

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

An integer overflow vulnerability in the WebGPU graphics component allows attackers to cause a denial-of-service condition, potentially crashing the Firefox or Thunderbird application.

MitigationUpdate to Firefox 150 or Thunderbird 150 or later to apply the patched WebGPU integer overflow fix.

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:< 150.0
ThunderbirdApplication
Affected:< 150.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Mozilla Firefox is installed
    On Windows, check Program Files/Mozilla Firefox or look for firefox.exe. On Linux, run 'which firefox' or check /usr/bin/firefox. On macOS, check /Applications/Firefox.app
    Affected if Firefox is installed and version is below 150.0
  2. Check Firefox version number
    Run 'firefox --version' from command line, or go to Firefox menu > Help > About Firefox to view the exact version
    Affected if Version displayed is below 150.0 (for example, 149.x, 148.x, etc.)
  3. Check if Mozilla Thunderbird is installed
    On Windows, check Program Files/Mozilla Thunderbird or look for thunderbird.exe. On Linux, run 'which thunderbird' or check /usr/bin/thunderbird. On macOS, check /Applications/Thunderbird.app
    Affected if Thunderbird is installed and version is below 150.0
  4. Check Thunderbird version number
    Run 'thunderbird --version' from command line, or go to Thunderbird menu > Help > About Thunderbird to view the exact version
    Affected if Version displayed is below 150.0 (for example, 149.x, 148.x, etc.)
  5. Verify if WebGPU is enabled in the browser
    In Firefox, type 'about:config' in the address bar, search for 'webgpu.enabled' or 'dom.webgpu.enabled' and check the boolean value
    Affected if WebGPU is enabled (set to true) in a Firefox or Thunderbird version below 150.0

You are affected if you have Firefox or Thunderbird installed with a version number below 150.0 AND WebGPU is enabled in the application settings.

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

Update to Firefox 150 or Thunderbird 150 or later to apply the patched WebGPU integer overflow fix.

Recommended fix High confidence

Firefox 150.0 and Thunderbird 150.0

  1. 1. Check current Firefox version: Open Firefox, go to Menu > Help > About Firefox (or navigate to about:support)
  2. 2. Check current Thunderbird version: Open Thunderbird, go to Menu > Help > About Thunderbird
  3. 3. For Firefox: If version is below 150.0, select 'Update to Firefox 150.0' or download Firefox 150.0 from the official Mozilla website (www.mozilla.org)
  4. 4. For Thunderbird: If version is below 150.0, download Thunderbird 150.0 from the official Mozilla website (www.mozilla.org)
  5. 5. Restart the application after updating
  6. 6. Verify the update was successful by checking the version again (should show 150.0 or higher)
Caveat Major version upgrades may have compatibility implications for extensions, add-ons, or older system requirements; review release notes before updating

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

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.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-6773 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-6773 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