CVE-2025-9179
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 · uneditedAn attacker was able to perform memory corruption in the GMP process which processes encrypted media. This process is also heavily sandboxed, but represents slightly different privileges from the content process. This vulnerability was fixed in Firefox 142, Firefox ESR 115.27, Firefox ESR 128.14, Firefox ESR 140.2, Thunderbird 142, Thunderbird 128.14, and Thunderbird 140.2.
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 memory corruption vulnerability exists in Firefox's GMP (Gecko Media Plugin) process, which handles decryption and processing of encrypted media content. While the GMP process runs in a sandbox, it operates with slightly elevated privileges compared to the content process, allowing an attacker to achieve memory corruption that could lead to arbitrary code execution.
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.27.0< 142.0>= 128.0, < 128.14.0>= 140.0, < 140.2.0< 128.14.0< 142.0>= 140.0, < 140.2.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, go to Help > About Firefox (or navigate to about:support). Note the version number displayed.Affected if The version is less than 115.27.0, OR between 128.0.0 and 128.13.x inclusive, OR between 140.0.0 and 140.1.x inclusive, OR less than 142.0.
-
Check Thunderbird versionOpen Thunderbird, go to Help > About Thunderbird. Note the version number displayed.Affected if The version is less than 128.14.0, OR between 140.0.0 and 140.1.x inclusive, OR less than 142.0.
-
Identify if GMP plugins are in useNavigate to about:support in Firefox or Thunderbird. Look for 'GMP' entries in the 'Media' or 'Plugins' section. Common GMP plugins include Widevine (CDP), Clearkey, or other DRM-related plugins.Affected if Any GMP plugin (Widevine, Clearkey, or similar DRM modules) is listed as installed or active in about:support.
-
Check for GMP plugin process activityIn Firefox/Thunderbird, navigate to about:processes. Look for a 'GMP' or 'GeckoMediaPlugin' process entry running alongside the main browser process.Affected if A GMP process is actively running, indicating the GMP subsystem is enabled and processing media.
You are affected if you run Firefox or Thunderbird with a version number matching the affected ranges AND have GMP plugins (such as Widevine or Clearkey for DRM content) installed or enabled.
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.27.0128.14.0140.2.0
Update affected installations to Firefox 142, Firefox ESR 115.27/128.14/140.2, or Thunderbird 142/128.14/140.2. Organizations should deploy these updates through their standard patch management processes.
Firefox 142 / Firefox ESR 115.27+ / Firefox ESR 128.14+ / Firefox ESR 140.2+ / Thunderbird 142 / Thunderbird 128.14+ / Thunderbird 140.2+ (specific version depends on current release channel)
- Check current Firefox or Thunderbird version via Help > About Firefox/Thunderbird or running 'firefox --version' or 'thunderbird --version' in terminal
- If running Firefox stable < 142.0, upgrade to Firefox 142 or later
- If running Firefox ESR 115.x < 115.27.0, upgrade to Firefox ESR 115.27 or later
- If running Firefox ESR 128.x < 128.14.0, upgrade to Firefox ESR 128.14 or later
- If running Firefox ESR 140.x < 140.2.0, upgrade to Firefox ESR 140.2 or later
- If running Thunderbird < 128.14.0, upgrade to Thunderbird 128.14 or later
- If running Thunderbird 140.x < 140.2.0, upgrade to Thunderbird 140.2 or later
- If running Thunderbird < 142.0, upgrade to Thunderbird 142 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9179 — 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-9179 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