CVE-2025-14322
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 · uneditedSandbox escape due to incorrect boundary conditions in the Graphics: CanvasWebGL component. This vulnerability was fixed in Firefox 146, Firefox ESR 115.31, Firefox ESR 140.6, Thunderbird 146, and Thunderbird 140.6.
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 sandbox escape vulnerability exists in the Graphics: CanvasWebGL component of Firefox and Thunderbird due to incorrect boundary conditions. This allows an attacker to bypass the security sandbox that isolates untrusted web content, potentially enabling arbitrary code execution. The vulnerability was addressed in the specified patched versions.
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< 115.31.0< 146.0>= 116.0, < 140.6.0< 140.6.0< 146.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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Firefox versionOpen Firefox and navigate to Menu > Help > About Firefox, or run 'firefox --version' from command lineAffected if The version shown is less than 115.31.0, or between 116.0 and 140.6.0 exclusive, or less than 146.0
-
Identify installed Thunderbird versionOpen Thunderbird and navigate to Menu > Help > About Thunderbird, or run 'thunderbird --version' from command lineAffected if The version shown is less than 140.6.0 or less than 146.0
-
Verify WebGL is enabled in FirefoxIn Firefox address bar, type 'about:config' and press Enter. Search for 'webgl.disabled' preference. If the value is 'false', WebGL is enabled. If 'true', WebGL is disabled.Affected if WebGL is enabled (webgl.disabled is false) AND the Firefox version falls within the affected ranges
-
Verify WebGL is enabled in ThunderbirdIn Thunderbird, WebGL settings may be accessible via profiles or registry. Check the application config for webgl.disabled preference.Affected if WebGL is enabled AND the Thunderbird version falls within the affected ranges
-
Confirm sandbox configurationThe vulnerability is a sandbox escape. If the browser security sandbox has been disabled via --no-sandbox flag or security.sandbox.content.disableAtStartup preferences, the impact of a successful exploit could be greater.Affected if The sandbox is explicitly disabled or reduced in effectiveness
A user is affected if they run a Firefox or Thunderbird version within the affected ranges AND have WebGL enabled, as the vulnerability exists in the CanvasWebGL component.
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 · scoped115.31.0140.6.0146.0
Update Firefox installations to version 146 (or ESR 115.31/140.6) and Thunderbird to version 140.6 to remediate this vulnerability.
Firefox 146 (standard), Firefox ESR 115.31 (ESR 115.x branch), Firefox ESR 140.6 (ESR 140.x branch), Thunderbird 146 (standard), or Thunderbird 140.6 (ESR)
- 1. Determine which Firefox or Thunderbird version is currently installed (Help > About Firefox/Thunderbird)
- 2. For Firefox users: If using standard release, upgrade to Firefox 146 or later
- 3. For Firefox ESR users: Determine if using ESR 115.x or ESR 140.x branch
- 4. If on Firefox ESR 115.x, upgrade to Firefox ESR 115.31 or later
- 5. If on Firefox ESR 140.x, upgrade to Firefox ESR 140.6 or later
- 6. For Thunderbird users: If using standard release, upgrade to Thunderbird 146 or later
- 7. For Thunderbird ESR users, upgrade to Thunderbird 140.6 or later
- 8. Restart the application after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14322 — 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-2025-14322 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