GStreamer rtpqdm2depay Out-Of-Bounds Write 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 payload elements. When parsing the packetid element, the process does not properly validate user-supplied data, which can result in a write past the end of an allocated array. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-28850.
Security readout for executives and security teams
Plain-English summary
CVE-2026-3083 is a high-severity GStreamer flaw that could let an attacker run code through crafted media/RTP input. The risk matters where business applications, browsers, media services, or pipelines process untrusted media using GStreamer. Public sources provided do not show CISA KEV listing or confirmed active exploitation.
Executive priority
Prioritize patching internet-facing or user-facing media-processing systems. The business risk is code execution in the affected process, but urgency should be based on actual GStreamer exposure because the provided evidence does not confirm active exploitation.
Technical view
The flaw is an out-of-bounds write in GStreamer rtpqdm2depay while processing X-QDM RTP payload elements. Packetid parsing lacks sufficient user-data validation, allowing writes past an allocated array. ZDI describes possible remote code execution in the current process context. CWE mappings include CWE-129 and CWE-787.
Likely exposure
Exposure is most likely in systems that use GStreamer to process RTP media, especially X-QDM payloads or untrusted media streams. Exact affected release ranges are incomplete in the bundle; one source names a specific GStreamer commit and Red Hat advisories provide downstream package context.
Exploitation context
The CVSS vector is network-accessible with low complexity and no privileges, but user or application interaction with the library is required. Attack vectors may vary by how GStreamer is embedded. No provided source confirms exploitation in the wild.
Researcher notes
Useful follow-up is version-range clarification across upstream and distributions. The source bundle identifies the vulnerable parser behavior and fix reference, but affected release mapping is sparse. Avoid assuming all GStreamer deployments are reachable unless the rtpqdm2depay path processes attacker-controlled media.
Mitigation direction
Apply vendor GStreamer updates from your operating system or application supplier.
For Red Hat environments, review the listed RHSA advisories for package status.
If building from source, confirm inclusion of upstream commit d60a94dee3c0a0942c9981491bf83e0de1900fbf.
Reduce untrusted RTP or X-QDM media processing until patched.
Track vendor guidance where affected version mapping remains unclear.
Validation and detection
Inventory systems and applications that load GStreamer media-processing components.
Check whether RTP depayloading or X-QDM payload handling is enabled or reachable.
Compare installed GStreamer packages against vendor errata and advisories.
Confirm patched builds include the upstream fix commit or downstream backport.
Review service boundaries where untrusted media reaches GStreamer.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-129: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
22Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-129 · source CWE mapping
Improper Validation of Array Index
Improper Validation of Array Index represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.