dbcve.org
FirefoxWeb browser · Mozilla

CVE-2026-8967

HIGH · 7.5 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 151.0.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
Information disclosure in the Graphics: WebGPU component. This vulnerability was fixed in Firefox 151 and Thunderbird 151.

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

Information disclosure vulnerability in the WebGPU graphics component of Firefox and Thunderbird. The flaw allows potential unauthorized access to sensitive information through the WebGPU API. Fixed in Firefox 151 and Thunderbird 151.

MitigationUpdate Firefox and Thunderbird installations to version 151 or later to apply the patched WebGPU component.

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:< 151.0.0
ThunderbirdApplication
Affected:< 151.0.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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Check Firefox version
    Navigate to Menu > Help > About Firefox, or enter 'about:support' in the address bar. The version number is displayed at the top of the page.
    Affected if Version shown is below 151.0.0 (for example, 150.x or earlier)
  2. Check Thunderbird version
    Navigate to Menu > Help > About Thunderbird. The version number is displayed in the dialog window.
    Affected if Version shown is below 151.0.0 (for example, 150.x or earlier)
  3. Verify if WebGPU is enabled
    In the address bar, enter 'about:config' and press Enter. Search for the preference named 'dom.webgpu.enabled'. Check the value column - true means enabled, false means disabled.
    Affected if The preference 'dom.webgpu.enabled' is set to true (enabled)
  4. Confirm WebGPU API presence
    In Firefox, enter 'about:support' and look for the 'WebGPU' entry in the Graphics section. If WebGPU is listed and active, the feature is available to web content.
    Affected if WebGPU appears as available or enabled in the browser's graphics support information

You are affected if your Firefox or Thunderbird version is below 151.0.0 AND WebGPU is enabled in the browser 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 151.0.0 or later
Fixed in 151.0.0
Interim mitigation

Update Firefox and Thunderbird installations to version 151 or later to apply the patched WebGPU component.

Recommended fix High confidence

Firefox 151.0.0 and Thunderbird 151.0.0

  1. Close Firefox and Thunderbird completely before starting the upgrade
  2. For Firefox: Open Firefox, go to Help > About Firefox, and click 'Check for Updates' to download and install version 151.0.0 or later
  3. For Thunderbird: Open Thunderbird, go to Help > About Thunderbird, and click 'Check for Updates' to download and install version 151.0.0 or later
  4. Alternatively, download the latest version directly from the official Mozilla website (www.mozilla.org) for your platform
  5. Run the installer and follow the prompts to complete the upgrade
  6. Restart the application after the upgrade completes
  7. Verify the installed version is 151.0.0 or higher by checking Help > About to confirm the vulnerability is addressed

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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