dbcve.org
GstreamerApplication

CVE-2025-2759

HIGH · 7.8 CVSS v3.1 Published 2025-05-22
Fix available
A fix is available. Upgrade to 1.25.1 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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
GStreamer Incorrect Permission Assignment Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of GStreamer. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the product installer. The issue results from incorrect permissions on folders. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of a target user. Was ZDI-CAN-25448.

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 confidence

GStreamer's Windows installer creates folders with overly permissive access control lists (ACLs), allowing unprivileged users to modify files in privileged locations. Once an attacker obtains low-privileged code execution, they can replace or modify executable files in these misconfigured folders to achieve privilege escalation to the target user's context.

MitigationApply the vendor-released security update for GStreamer to obtain a correctly-configured installer, then reinstall or correct folder permissions on existing installations to remove excessive access granted to standard users.

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
GstreamerApplication
Affected:< 1.25.1

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Verify GStreamer is installed on Windows
    Check for GStreamer installation by searching for gstreamer-related folders in common locations such as C:\Program Files\GStreamer, C:\Program Files (x86)\GStreamer, or use the Windows search feature to find gstreamer* directories
    Affected if GStreamer is found installed on the system
  2. Determine installed GStreamer version
    Look for a version file or check the properties of the GStreamer installation folder, typically found in the main gstreamer directory or within a '1.0' subfolder
    Affected if The installed version is less than 1.25.1
  3. Identify GStreamer installation directories
    Locate all directories where GStreamer is installed, commonly under C:\Program Files\GStreamer or C:\Program Files (x86)\GStreamer with version subdirectories like 1.0
    Affected if Multiple directories exist with broad installation paths
  4. Inspect folder ACLs on GStreamer directories
    Right-click on GStreamer installation folders, select Properties, then go to the Security tab. Check which users and groups have Full Control or Modify permissions, particularly looking for whether standard users or the 'Users' group have write access to directories containing executable files (.exe, .dll)
    Affected if Standard users or the 'Users' group have Full Control or Modify permissions on folders containing executable files in privileged installation locations

A user is affected if GStreamer version 1.25.1 or later is not installed AND folder permissions allow unprivileged users to modify executable files in GStreamer installation directories.

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 1.25.1 or later
Fixed in 1.25.1
Interim mitigation

Apply the vendor-released security update for GStreamer to obtain a correctly-configured installer, then reinstall or correct folder permissions on existing installations to remove excessive access granted to standard users.

Recommended fix Moderate confidence

GStreamer 1.25.1 or later

  1. 1. Identify the currently installed GStreamer version by checking your system package manager or installed binaries
  2. 2. If using a package manager (apt, yum, dnf, pacman, etc.), update to the latest available GStreamer package
  3. 3. For systems with manually installed GStreamer, download GStreamer version 1.25.1 or later from the official source (gstreamer.freedesktop.org)
  4. 4. Reinstall GStreamer using the updated installer to ensure correct folder permissions are applied
  5. 5. Verify the installed version is 1.25.1 or later using 'gst-inspect-1.0 --version' or equivalent
  6. 6. Confirm that the GStreamer installation directories have appropriate permissions (typically 755 for directories, 644 for files, owned by root:root or appropriate system user)

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

Fix this in Gstreamer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2759 — 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-2759 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