FirefoxWeb browser · Mozilla
CVE-2025-13023
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: WebGPU component. This vulnerability was fixed in Firefox 145 and Thunderbird 145.
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 · moderate confidenceA sandbox escape vulnerability exists in the WebGPU graphics component of Firefox and Thunderbird due to incorrect boundary conditions. This flaw allows a remote attacker to potentially break out of the sandboxed execution environment and execute arbitrary code with elevated privileges. The vulnerability was patched in Firefox 145 and Thunderbird 145.
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
< 145.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 Firefox versionOpen Firefox, click the menu button (three horizontal lines), select Help, then About Firefox. The version number will display in the window that opens.Affected if The displayed version is below 145.0 (e.g., 144.0, 143.0, etc.) and WebGPU is enabled or used.
-
Check Thunderbird versionOpen Thunderbird, click the menu button, select Help, then About Thunderbird. The version number will display in the window that opens.Affected if The displayed version is below 145.0 and WebGPU is enabled or used.
-
Verify WebGPU is in useIn Firefox, type about:support in the address bar and search for WebGPU to confirm the feature is present and active in the browser environment.Affected if WebGPU is enabled and the browser version is below 145.0.
-
Confirm component exposureWebGPU is a graphics API accessible through web content. Check if any internal pages, testing interfaces, or web applications on the system utilize or test WebGPU functionality.Affected if WebGPU is actively being used or was recently used in the browser and the version is below 145.0.
You are affected if either Firefox or Thunderbird is installed at a version below 145.0 and WebGPU feature is enabled or accessible in the browser environment.
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 · scoped145.0
Upgrade to Firefox 145 or Thunderbird 145 or later to remediate this critical sandbox escape vulnerability.
Firefox 145.0
- Upgrade Firefox to version 145.0 or later by downloading from the official Mozilla website (www.mozilla.org) or using the built-in update mechanism (Help > About Firefox > Check for 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
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13023 — 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-13023 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