Skip to main content
Mallory
HighVulnerability

CVE-2026-3083: Remote Code Execution in GStreamer rtpqdm2depay

Published Mar 13, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.8High · v3.1
EPSS0.95%62nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Gstreamer
IdentifiersCVE-2026-3083CWE-787 · Out-of-bounds Write

CVE-2026-3083 is an out-of-bounds write vulnerability in the rtpqdm2depay RTP QDM2 depayloader in GStreamer's gst-plugins-good package. During processing of X-QDM RTP payloads, insufficient validation of the attacker-controlled packetid element allows a write beyond an allocated array. A remote attacker who causes an application to process a crafted payload through the vulnerable element can potentially execute arbitrary code in the context of the hosting process. The vulnerability is also tracked as ZDI-26-166 and ZDI-CAN-28850.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause an application crash or arbitrary code execution with the privileges of the process using GStreamer. Code execution can compromise the confidentiality and integrity of data accessible to that process and disrupt application availability. The vulnerability has a CVSS v3.1 base score of 8.8 with vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Mitigation

If you can’t patch tonight, do this now.

Disable the rtpqdm2depay RTP QDM2 depayloader so applications cannot process untrusted X-QDM RTP payloads through it. The element should not be used; the QDM2 streaming format has not been in active use for well over a decade.

Remediation

Patch, then assume compromise.

Upgrade gst-plugins-good to version 1.28.1 or a subsequent release incorporating the fix. Version 1.28.1 addresses the issue by disabling the RTP QDM2 depayloader entirely. For older GStreamer branches, apply the vendor-provided patch and rebuild, or install the distribution's patched packages. Fixed Debian packages include gst-plugins-good1.0 version 1.22.0-5+deb12u4 for Debian 12 Bookworm and 1.26.2-1+deb13u2 for Debian 13 Trixie.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GstreamerGstreamerapplication
FAQ

Frequently asked questions

Is CVE-2026-3083 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-3083 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-3083?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-3083.
Is there a patch for CVE-2026-3083?
Upgrade gst-plugins-good to version 1.28.1 or a subsequent release incorporating the fix. Version 1.28.1 addresses the issue by disabling the RTP QDM2 depayloader entirely.
What products are affected by CVE-2026-3083?
Gstreamer.
How severe is CVE-2026-3083?
CVE-2026-3083 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.95% (62nd percentile) as of Nov 19, 2026.
Activity feed

Recent activity

21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+2 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity7Community discussion across Reddit, Mastodon, and other social sources.