dbcve.org
GstreamerApplication

CVE-2026-3085

HIGH · 8.8 CVSS v3.1 Published 2026-03-16
Fix available
A fix is available. Upgrade to 1.28.1 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
GStreamer rtpqdm2depay Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. Interaction with this library is required to exploit this vulnerability but attack vectors may vary depending on the implementation. The specific flaw exists within the processing of X-QDM RTP payloads. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-28851.

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

GStreamer's rtpqdm2depay element contains a heap-based buffer overflow vulnerability in its handling of X-QDM RTP payloads. The flaw results from insufficient validation of user-supplied data length before copying into a heap-allocated buffer, enabling remote attackers to achieve arbitrary code execution in the context of the current process.

MitigationApply vendor patches for GStreamer when available; until then, disable or restrict processing of X-QDM RTP streams and isolate GStreamer-based applications behind network segmentation to limit exposure to untrusted RTP sources.

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.28.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
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. Check installed GStreamer version
    Run 'gst-inspect-1.0 --version' or 'pkg-config --modversion gstreamer-1.0' to determine the installed GStreamer core library version
    Affected if Version is lower than 1.28.1
  2. Verify rtpqdm2depay element availability
    Execute 'gst-inspect-1.0 rtpqdm2depay' to confirm the element is registered and available in the GStreamer installation
    Affected if The element loads successfully without errors, indicating it is present and usable
  3. Identify active use of rtpqdm2depay in pipelines
    Search configuration files, application logs, and running processes for instances of 'rtpqdm2depay' in GStreamer pipeline definitions
    Affected if Any pipeline or application is actively using the rtpqdm2depay element to process RTP streams
  4. Assess RTP input sources
    Review network configurations and application settings to determine if the system accepts RTP streams from untrusted or external network sources
    Affected if RTP input from untrusted sources is permitted and processed by vulnerable GStreamer pipelines

The environment is affected if GStreamer version is below 1.28.1 AND the rtpqdm2depay element is either available for use or actively processing RTP payloads from untrusted sources.

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.28.1 or later
Fixed in 1.28.1
Interim mitigation

Apply vendor patches for GStreamer when available; until then, disable or restrict processing of X-QDM RTP streams and isolate GStreamer-based applications behind network segmentation to limit exposure to untrusted RTP sources.

Recommended fix High confidence

GStreamer 1.28.1 or later

  1. Identify the current GStreamer version installed in your environment using your system's package manager (e.g., `gst-inspect-1.0 --version` or `dpkg -l | grep gstreamer` for Debian-based systems)
  2. Update the GStreamer packages to version 1.28.1 or later. For Debian/Ubuntu: `sudo apt update && sudo apt install libgstreamer1.0-dev gstreamer1.0-plugins-base gstreamer1.0-plugins-good` or specific package names containing rtpqdm2depay
  3. For Red Hat-based systems: `sudo yum update gstreamer*` or `sudo dnf update gstreamer*`
  4. Verify the upgrade was successful by checking the version: `gst-inspect-1.0 --version`
  5. Ensure the rtpqdm2depay element is available: `gst-inspect-1.0 rtpqdm2depay`
  6. Test that media pipelines utilizing RTP depayloading function correctly after the update

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

Fix this in Gstreamer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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