FirefoxWeb browser · Mozilla
CVE-2025-14860
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 Disability Access APIs component. This vulnerability was fixed in Firefox 146.0.1.
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 use-after-free vulnerability exists in Firefox's Disability Access APIs component. Use-after-free bugs occur when memory is accessed after it has been freed, potentially allowing arbitrary code execution or memory corruption. This critical flaw was addressed in Firefox version 146.0.1.
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
< 146.0.1CVSS 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 version via About dialogOpen Firefox, click the menu button (three horizontal lines), select Help, then select About Firefox. The version number is displayed in the window that opens.Affected if The displayed version number is less than 146.0.1 (for example, 146.0, 145.x, or earlier)
-
Check Firefox version via command line (Windows)Open Command Prompt and run: "C:\Program Files\Mozilla Firefox\firefox.exe" -v or check the version property of the executable file in File Explorer.Affected if The version shown is less than 146.0.1
-
Check Firefox version via command line (macOS)Open Terminal and run: /Applications/Firefox.app/Contents/MacOS/firefox -vAffected if The version shown is less than 146.0.1
-
Check Firefox version via command line (Linux)Open Terminal and run: firefox --versionAffected if The version shown is less than 146.0.1
A user is affected if their installed Firefox version is any version lower than 146.0.1, since the use-after-free vulnerability in the Disability Access APIs component exists in all prior 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 · scoped146.0.1
Update Firefox to version 146.0.1 or later. Organizations should deploy the updated browser version across all affected systems and verify successful remediation.
Firefox 146.0.1
- Check current Firefox version by navigating to about:support or going to Menu > Help > About Firefox
- Download Firefox 146.0.1 from the official Mozilla website (www.mozilla.org) or use the built-in update mechanism
- If using the downloaded installer, run it and follow the prompts to install the update
- If using the built-in updater, click 'Update to 146.0.1' when prompted and restart Firefox
- After updating, verify the version by checking about:support to confirm Firefox 146.0.1 is installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14860 — 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-14860 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