CVE-2025-10528
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 undefined behavior, invalid pointer in the Graphics: Canvas2D component. This vulnerability was fixed in Firefox 143, Firefox ESR 140.3, Thunderbird 143, and Thunderbird 140.3.
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: Canvas2D component of Firefox and Thunderbird due to undefined behavior causing an invalid pointer dereference. This could allow an attacker to break out of the sandboxed environment and potentially execute arbitrary code. The vulnerability was addressed in Firefox 143, Firefox ESR 140.3, Thunderbird 143, and Thunderbird 140.3.
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< 140.3.0< 143.0< 140.3.0>= 141.0, < 143.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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 the installed productCheck if Firefox or Thunderbird is installed. On Windows, look in Program Files. On macOS, check /Applications. On Linux, check package manager or which firefox thunderbird.Affected if The system has Firefox or Thunderbird installed
-
Determine the installed Firefox versionFor Firefox: Enter 'about:support' in the address bar, or run 'firefox --version' from command line. Look for the version number in the 'Application Basics' section.Affected if Firefox version is less than 140.3.0 or is between 141.0 and 142.x (less than 143.0)
-
Determine the installed Thunderbird versionFor Thunderbird: Enter 'about:support' in the address bar, or run 'thunderbird --version' from command line. Look for the version number.Affected if Thunderbird version is less than 140.3.0 or is between 141.0 and 142.x (less than 143.0)
-
Verify the Canvas2D component is in useThe vulnerability exists in the Graphics: Canvas2D component. This component is enabled by default in Firefox and Thunderbird for rendering web content and emails with graphics. No special configuration check needed - it is part of the standard rendering pipeline.Affected if The application processes HTML content, web pages, or email with graphical elements (standard use case)
-
Confirm the sandbox is enabledThe vulnerability is a sandbox escape. Check that the sandbox setting has not been disabled. In Firefox, go to about:config and search for 'security.sandbox.content.level' (default is non-zero). In Thunderbird, check similar settings.Affected if The sandbox is enabled (this is the default and required for the vulnerability to be a sandbox escape)
The user is affected if they have Firefox versions < 140.3.0, or 141.x through 142.x, or Thunderbird versions < 140.3.0 or 141.x through 142.x, with the Canvas2D component in use (standard configuration).
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 · scoped140.3.0143.0
Apply the vendor-supplied patches by updating affected installations to Firefox 143 (or ESR 140.3) and Thunderbird 143 (or 140.3) or later versions.
Firefox 143 (or Firefox ESR 140.3) / Thunderbird 143 (or Thunderbird 140.3)
- Check current Firefox or Thunderbird version via Help > About Firefox/Thunderbird
- Download Firefox 143 from www.mozilla.org (or Firefox ESR 140.3 if using the ESR channel)
- Download Thunderbird 143 from www.mozilla.org (or Thunderbird 140.3 if using the standard release)
- Install the downloaded version
- Restart the browser or email client to apply the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10528 — 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-10528 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