FirefoxWeb browser · Mozilla
CVE-2026-12293
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 Graphics: WebGPU component. This vulnerability was fixed in Firefox 152 and Thunderbird 152.
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 confidenceA use-after-free vulnerability exists in the WebGPU graphics component of Firefox and Thunderbird. This memory safety issue occurs when the program continues to use a pointer after the memory it references has been freed, potentially allowing remote code execution or crash exploitation.
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
< 152.0.0< 152.0.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Firefox versionOpen Firefox, click the menu icon, select Help, then About Firefox. Alternatively, run 'firefox --version' from command line.Affected if The displayed version is below 152.0.0 (for example, 151.x.x or earlier)
-
Identify installed Thunderbird versionOpen Thunderbird, click the menu icon, select Help, then About Thunderbird. Alternatively, run 'thunderbird --version' from command line.Affected if The displayed version is below 152.0.0 (for example, 151.x.x or earlier)
-
Verify if WebGPU is enabled in FirefoxIn Firefox address bar, type 'about:config' and press Enter. In the search box, search for 'webgpu.enabled'. Check if the preference exists and its boolean value is set to true.Affected if WebGPU is enabled (value is true) AND the Firefox version is below 152.0.0
You are affected if either Firefox or Thunderbird is installed with a version below 152.0.0 and WebGPU is in use (enabled by default in affected versions).
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 · scoped152.0.0
Update Firefox and Thunderbird to version 152 or later to obtain the vendor-provided patch for this vulnerability.
Firefox 152.0.0 and Thunderbird 152.0.0
- Check current Firefox version: Open Firefox, go to Help > About Firefox
- Check current Thunderbird version: Open Thunderbird, go to Help > About Thunderbird
- Update Firefox: If version is below 152.0.0, use Help > Check for Updates or download version 152.0.0 from https://www.mozilla.org/firefox/
- Update Thunderbird: If version is below 152.0.0, use Help > Check for Updates or download version 152.0.0 from https://www.mozilla.org/thunderbird/
- Restart the applications after installing updates
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
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 locallyCheck whether your project pulls in CVE-2026-12293 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12293 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