Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted RTP L16 stream to pipeline
-
DeliveryOversized payload reaches rtpL16depay
-
ExploitUnvalidated length copied to heap buffer
-
ExecutionHeap buffer overflow corrupts memory
-
ImpactExecute arbitrary code as processing user
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the target application or GStreamer pipeline to actually use the rtpL16depay element to depayload attacker-supplied RTP L16 (16-bit linear PCM) audio, and the attacker must be able to deliver that RTP stream to the pipeline. Limiting factors: only GStreamer-based software that processes RTP L16 audio is affected (not every GStreamer deployment instantiates this element); the description explicitly states interaction with the library is required and that attack vectors vary by implementation, so a passive RTP receiver/server is effectively remotely exploitable while a client application may require a user to connect to or open a malicious stream. Code execution occurs only at the privilege level of the process hosting the pipeline. |
| Impact | Multiple signals point toward genuine high priority, but with one notable caveat. The CVSS 3.0 vector (AV:N/AC:L/PR:N/UI:N) describes network-reachable, low-complexity, unauthenticated exploitation with full CIA impact (9.8 CRITICAL), and the CWE-122 heap overflow with stated 'execute arbitrary code' impact is consistent with a high-technical-impact, memory-corruption RCE. This was reported through ZDI (ZDI-CAN-31143 / ZDI-26-775), a credible research source, and a vendor fix commit already exists in the GStreamer GitLab, which confirms the bug is real and patched. However, no EPSS score, no CISA KEV listing, and no public exploit were provided, so there is no evidence of active exploitation or weaponization - the risk is driven by severity and reachability, not by observed in-the-wild use. One explicit conflict must be flagged: the CVSS vector asserts UI:N (no user interaction), yet the description states 'Interaction with this library is required to exploit this vulnerability but attack vectors may vary depending on the implementation.' This means real-world exploitability is implementation-dependent - straightforward (effectively UI:N) for a server/pipeline that passively receives RTP L16 streams, but gated by user action for a client that must be pointed at a malicious stream. Verify the deployment mode before treating this as universally unauthenticated-remote. |
| Exploit ScenarioDerived | An attacker delivers a crafted RTP L16 audio stream to an application built on GStreamer whose pipeline uses the rtpL16depay element; the depayloader copies attacker-controlled payload data into a heap buffer without validating its length, overflowing it. By shaping the oversized payload the attacker corrupts heap metadata or adjacent objects to achieve arbitrary code execution in the context of the processing application. No public proof-of-concept was identified in the provided data, so exploitation currently requires original exploit development. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Heap-based buffer overflow in the GStreamer rtpL16depay element allows unauthenticated remote attackers to execute arbitrary code at the privilege level of the process hosting the pipeline. Only GStreamer-based software that actually instantiates rtpL16depay to depayload attacker-supplied RTP L16 (16-bit linear PCM) audio is exposed, so a passive RTP receiver or streaming server is effectively remotely exploitable while client-side applications may require the user to connect to a malicious stream. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has published an upstream fix commit but no tagged patched release has been independently confirmed.
RemediationAI
Apply the upstream fix from GStreamer GitLab commit 80c184b4c5ee8ba28b2540ba58f40b8d44b61622 (https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/80c184b4c5ee8ba28b2540ba58f40b8d44b61622) and upgrade to the first distribution or vendor release that incorporates it; because no tagged patched version has been independently confirmed, verify with your distro or GStreamer package maintainer that the commit is included before treating the system as fixed, and consult ZDI-26-775 for the vendor's advisory status. Where patching cannot be done immediately, remove or replace rtpL16depay in pipelines that process untrusted RTP L16 streams (for example by decoding to a validated format upstream or rejecting L16 payloads at the RTP demuxer), accepting that this breaks interoperability with legitimate L16 audio sources. Additionally, restrict who can deliver RTP to the pipeline by firewalling the RTP/UDP port range to trusted media peers, enabling SRTP or other session authentication where supported, and running the GStreamer host process with least privilege inside a container, seccomp sandbox, or dedicated unprivileged user so that any successful exploitation is contained; these controls reduce exposure but do not eliminate the overflow itself.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
RTP L16 is the standard real-time transport profile for uncompressed 16-bit linear PCM audio; the rtpL16depay element (part of GStreamer's RTP payload handling, typically shipped in gst-plugins-good) receives RTP packets and copies their payload into a heap-allocated output buffer for downstream decoding. The flaw is a classic CWE-122 heap-based buffer overflow: the element fails to validate the length of attacker-controlled payload data against the size of the destination buffer before the copy, so an oversized or crafted RTP payload can overflow the heap and corrupt adjacent memory. Because the vulnerable copy occurs inside a library element rather than a hardened standalone daemon, exploitability depends entirely on the surrounding application: the attack surface is the RTP stream delivered to the pipeline, and successful exploitation yields code execution in the context of the process hosting that pipeline. The CPE entry (cpe:2.3:a:gstreamer:gstreamer:*:*:*:*:*:*:*:*) marks all GStreamer versions as potentially affected, while the CVSS 3.0/3.1 vector (AV:N/AC:L/PR:N/UI:N) rates the issue as a network-reachable, unauthenticated, low-complexity remote code execution flaw with high confidentiality, integrity, and availability impact.
Know when Gstreamer gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
RTP stream is network-delivered (AV:N) with no auth (PR:N) and a straightforward length-validation flaw (AC:L); UI:N reflects passive RTP-receiver deployments, though client use cases may warrant UI:R.
Primary rating from Vendor (zdi).
CVSS VectorVendor: zdi
DescriptionCVE.org
GStreamer rtpL16depay 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 RTP payload elements. 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-31143.
Executive ViewAI
A critical heap-based buffer overflow in GStreamer's rtpL16depay element can let remote attackers execute code at the privilege level of any process that depayloads attacker-supplied RTP L16 audio, putting exposed streaming servers, passive RTP receivers, and media pipelines at direct risk. Because no tagged vendor patch release is confirmed, leadership should treat GStreamer deployments that instantiate this element as high-risk until mitigations are applied and a fixed release is verified.
No vendor-released patch identified; disable or remove rtpL16depay from GStreamer pipelines, restrict RTP L16 ingestion to trusted networks and senders, segment and least-privilege affected streaming processes, monitor for crashes or exploitation attempts, and apply the upstream fix commit only after validation.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Heap-based buffer overflow in the flx_decode_delta_fli function in gst/flx/gstflxdec.c in the FLIC decoder in GStreamer
Heap-based buffer overflow in the flx_decode_delta_fli function in gst/flx/gstflxdec.c in the FLIC decoder in GStreamer
Heap-based buffer overflow in the flx_decode_delta_fli function in gst/flx/gstflxdec.c in the FLIC decoder in GStreamer
The FLIC decoder in GStreamer before 1.10.2 allows remote attackers to cause a denial of service (out-of-bounds write an
A heap-based buffer overflow vulnerability exists in GStreamer's RTSP connection parser that allows remote attackers to
A heap buffer over-read vulnerability exists in GStreamer's isomp4 plugin that allows reading past allocated memory boun
An integer overflow vulnerability in the GStreamer multimedia framework's matroska demuxer allows heap memory corruption
A critical integer overflow vulnerability in GStreamer's qtdemux element allows attackers to trigger denial of service o
A critical integer overflow vulnerability in the GStreamer multimedia framework's Matroska (MKV) demuxer can cause denia
An integer overflow vulnerability in GStreamer's Matroska demuxer can cause denial of service or potentially heap memory
An integer overflow vulnerability in GStreamer's AVI demux element allows attackers to trigger a heap overwrite when par
A heap overflow vulnerability exists in GStreamer's matroskaparse element due to an integer overflow in the gst_matroska
EUVD-2026-107395
GHSA-62fg-53h6-6f68
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB