CVE-2025-11709
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 · uneditedA compromised web process was able to trigger out of bounds reads and writes in a more privileged process using manipulated WebGL textures. This vulnerability was fixed in Firefox 144, Firefox ESR 115.29, Firefox ESR 140.4, Thunderbird 144, and Thunderbird 140.4.
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 compromised web process can exploit manipulated WebGL textures to trigger out-of-bounds memory reads and writes in a higher-privileged process, effectively escaping the browser sandbox. This represents a critical memory safety vulnerability in Firefox and Thunderbird's WebGL implementation.
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.29.0< 144.0>= 116.0, < 140.4.0< 144.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.
-
Check installed Firefox versionOpen Firefox, go to Menu > Help > About Firefox (or navigate to about:support). Note the version number displayed.Affected if The version is less than 115.29.0, OR less than 144.0, OR between 116.0 and 140.4.0 (inclusive of 140.4.0 is fixed)
-
Check installed Thunderbird versionOpen Thunderbird, go to Menu > Help > About Thunderbird. Note the version number displayed.Affected if The version is less than 144.0
-
Verify WebGL is accessible in FirefoxIn the Firefox address bar, navigate to about:support. Scroll to the 'Graphics' section and check if WebGL is listed as available or enabled.Affected if WebGL is enabled/available - the vulnerability requires WebGL to be reachable from web content
-
Check WebGL status in ThunderbirdThunderbird shares the same rendering engine. Check Help > About Thunderbird for the Gecko version, then verify if WebGL-enabled content could be rendered in any embedded browser components.Affected if WebGL is available in the underlying engine - the vulnerability exists in the shared rendering layer
You are affected if you run Firefox versions below 115.29.0, below 144.0, or between 116.0 and 140.4.0, or Thunderbird below 144.0, AND WebGL is enabled in your browser.
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.29.0140.4.0144.0
Upgrade immediately to Firefox 144, Firefox ESR 115.29/140.4, or Thunderbird 140.4 or later to remediate this critical sandbox escape vulnerability.
Firefox 144 / Firefox ESR 115.29 / Firefox ESR 140.4 / Thunderbird 144 / Thunderbird 140.4 (matching your current branch)
- 1. Identify which Mozilla product and version branch is in use (Firefox Standard, Firefox ESR, or Thunderbird)
- 2. For Firefox Standard users: Check current version in Menu > Help > About Firefox
- 3. For Firefox ESR users: Check current version in Menu > Help > About Firefox ( ESR label indicates ESR branch)
- 4. For Thunderbird users: Check current version in Menu > Help > About Thunderbird
- 5. If using Firefox Standard: Upgrade to version 144 or later
- 6. If using Firefox ESR 115.x: Upgrade to version 115.29 or later
- 7. If using Firefox ESR 140.x: Upgrade to version 140.4 or later
- 8. If using Thunderbird: Upgrade to version 144 or later (or 140.4 for ESR branch)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11709 — 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-11709 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