dbcve.org
FirefoxWeb browser · Mozilla

CVE-2025-1930

HIGH · 8.8 CVSS v3.1 Published 2025-03-04
Fix available
A fix is available. Upgrade to 115.21.0 / 128.8 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
On Windows, a compromised content process could use bad StreamData sent over AudioIPC to trigger a use-after-free in the Browser process. This could have led to a sandbox escape. This vulnerability was fixed in Firefox 136, Firefox ESR 115.21, Firefox ESR 128.8, Thunderbird 136, and Thunderbird 128.8.

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 confidence

A compromised content process on Windows can send malformed StreamData over the AudioIPC channel to trigger a use-after-free vulnerability in the Browser process. This memory corruption could allow an attacker to escape the content process sandbox and potentially execute code in the Browser process context.

MitigationUpdate Firefox to version 136 or later, Firefox ESR to 128.8 or later (or 115.21), and Thunderbird to 136 or 128.8 or later. In enterprise environments, prioritize updating systems with elevated privileges or browser-facing roles.

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
Affected:< 115.21.0< 136.0>= 116.0, < 128.8.0
ThunderbirdApplication
Affected:< 128.8> 1.28.8, < 136.0

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Windows platform
    Confirm the system is running Microsoft Windows (the vulnerability only affects Windows)
    Affected if Running any version of Firefox or Thunderbird on Windows
  2. Check Firefox version
    Open Firefox, go to Menu > Help > About Firefox, or navigate to about:support, to view the installed version number
    Affected if Version is < 115.21.0, or >= 116.0 and < 128.8.0, or < 136.0 (for versions 116.0 through 135.x)
  3. Check Thunderbird version
    Open Thunderbird, go to Menu > Help > About Thunderbird to view the installed version number
    Affected if Version is > 1.28.8 and < 128.8, or < 136.0 (for versions 128.x through 135.x)

User is affected if running Firefox or Thunderbird on Windows with a version number that falls below 136.0 (or below 128.8.0 for the 128.x ESR branch, or below 115.21.0 for the 115.x ESR branch).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 115.21.0 / 128.8 / 128.8.0 or later
Fixed in 115.21.0128.8128.8.0
Interim mitigation

Update Firefox to version 136 or later, Firefox ESR to 128.8 or later (or 115.21), and Thunderbird to 136 or 128.8 or later. In enterprise environments, prioritize updating systems with elevated privileges or browser-facing roles.

Recommended fix High confidence

Firefox 136.0+ (or Firefox ESR 115.21+ / ESR 128.8+); Thunderbird 128.8+ (or 136.0+)

  1. Identify the currently installed Firefox or Thunderbird version via Help > About (or running 'firefox --version' / 'thunderbird --version' in terminal)
  2. Close all browser/mail client instances
  3. For Firefox: Download and install Firefox 136.0 or later from mozilla.org, or for ESR users download either Firefox ESR 115.21 or ESR 128.8 from mozilla.org
  4. For Thunderbird: Download and install Thunderbird 128.8 or later (or 136.0+) from mozilla.org
  5. Restart the application and verify the version via Help > About to confirm the update was applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1930 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1930 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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