gst-plugins-base's RTSP support library (subprojects/gst-plugins-base/gst-libs/gst/rtsp/gstrtspmessage.c) implements gstrtspmessageparseauthcredentials(), used by both gst-rtsp-server (to parse a client's Authorization header, gst-rtsp-server/gst/rtsp-server/rtsp-auth.c:861, defaultauthenticate()) and by RTSP clients such as gstrtspsrc (gst-plugins-good/gst/rtsp/gstrtspsrc.c:6966) and rtspclientsink (gst-rtsp-sink/gstrtspclientsink.c:2737) to parse a server's WWW-Authenticate header. The internal helper parseauthcredentials() (gstrtspmessage.c, static function, ~line 1362) tokenizes comma-separated auth-param name=value pairs. For each parameter it computes itemend = skipitem(header) (the end of the current token, which points AT the whitespace/comma/NUL character that terminated the token, not past it), then does value = skiplws(eq + 1); authparam->value = gstrndup(value, itemend - value); (line ~1421-1425). skiplws() has no awareness of itemend: if the character skipitem() used as the token terminator happens to be whitespace, skiplws() will step over it (and any further whitespace) looking for a non-space character, potentially advancing value past itemend. This makes itemend - value a negative ptrdifft, which is implicitly converted to gsize (an unsigned 64-bit value near GMAXSIZE) when passed to gstrndup(). Because n+1 (computed inside gstrndup) wraps to 0 on the -1 case, gnew(gchar, 0) resolves to gmalloc(0), which by GLib's documented contract returns NULL; strncpy() is then invoked with this NULL destination and n=GMAXSIZE, corrupting/crashing, and even where gstrndup does return, the resulting NULL is stored into authparam->value without a NULL check. Immediately afterward the code does if (value[0] == '"') decodequotedstring(authparam->value); -- value[0] here is checked on the original (non-NULL) source pointer, so the branch can be taken even though authparam->value is NULL, and decodequotedstring() dereferences the NULL pointer, causing SIGSEGV. Reporter (Roy Lau, royworking98) reported this to the GStreamer security contacts on 2026-08-26 (gitlab.freedesktop.org/gstreamer/gstreamer/-/workitems/5278), and the maintainers merged a fix at gitlab.freedesktop.org/gstreamer/gstreamer-security/-/mergerequests/120 on 2026-09-02, targeting the 1.28.7 release. Reporter tested against gstreamer <= 1.28.2; the vulnerable code path is present up to (and reportedly including) versions prior to 1.28.7. Verified independently via static source review against the 1.28.2 tag; dynamic PoC execution was not performed. PSIRT Ticket: PSIRTSUPT-23042 (GST-SA-2026-0082).

GStreamer MRF File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the parsing of MRF files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-29510.

GStreamer PNG File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the parsing of PNG files. 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-29581.

GStreamer MRF File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the parsing of MRF files. 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-29608.

GStreamer OGG File Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the parsing of OGG files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-29584.

A flaw was found in GStreamer gst-plugins-good (avidemux). In gstavidemuxriffparsevprp(), the number of available gstriffvprpvideofielddesc entries is calculated by dividing the remaining buffer size by the attacker-controlled vprp->fields value, rather than by sizeof(gstriffvprpvideofielddesc). This can cause the parser to treat more field descriptors as available than fit in the input buffer, resulting in out-of-bounds reads. Processing a crafted AVI via playbin/decodebin can crash the application (denial of service). Fixed upstream in gst-plugins-good 1.28.6 (GStreamer-SA-2026-0072).

A flaw was found in GStreamer gst-plugins-good (avidemux). When parsing FUJIFILM metadata in an AVI strd chunk, gstavidemuxparsestrd() decrements a remaining-length counter by fixed offsets (98 and 10 bytes) without verifying sufficient data remains. For crafted strd payloads of exactly 106 or 107 bytes, the counter underflows to a very large unsigned value, causing subsequent null-terminated string scanning to read far beyond the allocated heap buffer. Date-format normalization may also write beyond the buffer end. Confirmed impacts include heap out-of-bounds read, out-of-bounds write, heap information disclosure (adjacent data appearing in parsed metadata), and application crash/denial of service. The avidemux element is auto-plugged by playbin, decodebin, and gst-discoverer, so opening or previewing a crafted AVI is sufficient to trigger the issue. Fixed upstream in gst-plugins-good 1.28.6 (GStreamer-SA-2026-0072).

This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of PNG files. 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.

This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of PNG files. 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.

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 validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process.

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 validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process.

This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of OGG files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process.

This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of OGG files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process.

This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of MRF files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process.

This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of MRF files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process.

This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of MRF files. 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.

This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of MRF files. 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.

GStreamer MRF File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the parsing of MRF files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-29510.

GStreamer PNG File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the parsing of PNG files. 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-29581.

GStreamer MRF File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the parsing of MRF files. 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-29608.

GStreamer OGG File Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the parsing of OGG files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-29584.

GStreamer rtpsbcdepay Use-After-Free 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 validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-29787.

A 1-byte heap out-of-bounds read vulnerability exists in the gsth264parseprocessnal() function in subprojects/gst-plugins-bad/gst/videoparsers/gsth264parse.c. The function processes H.264 NAL units including GSTH264NALSLICEEXT (NAL type 20) for MVC/SVC extension slices. At line 1132, the code dereferences (nalu->data + nalu->offset + nalu->headerbytes) to check the firstmbinslice flag without first verifying that nalu->size > nalu->headerbytes. For extension slice types, headerbytes is set to 4 (1 byte base + 3 bytes extension header per gsth264parser.c:243). A malformed NAL unit with exactly size==4 passes the minimum size check (size >= 2 at line 999) but triggers a 1-byte read at offset 4, which is beyond the allocated buffer. The same bounds check pattern is correctly implemented in gsth264parsecollectnal() at line 1259 with if (nalu->size > nalu->headerbytes). The vulnerability affects GStreamer 1.x versions (tested against git version 1.29.1.1). Upstream maintainer Sebastian Droege confirmed the vulnerability via GitLab work item 5108. Reported by Dr. Faruk Kazi, Ramesh Adhikari, and Ariba Afroz from CoE-CNDS Lab, VJTI, Mumbai, India. PSIRT Ticket: PSIRTSUPT-17585.

A flaw was found in the GStreamer gst-plugins-bad package. When processing a malformed H.266/VVC video stream with a crafted aspect ratio indicator value, the H.266 parser performs an out-of-bounds read of up to 8 bytes from adjacent memory. This flaw allows an attacker to craft a malicious H.266 video file or stream that, when processed by a GStreamer-based application, could leak limited memory contents through video metadata, potentially exposing sensitive information from the application's address space.

GStreamer H.265 buffering period SEI parser stack buffer overflow. In gsth265parserparsebufferingperiod(), the CPB loop bound used cpbcntminus1[i] instead of cpbcntminus1[0], causing writes past the 32-element CPB arrays on the stack. Fixed in GStreamer 1.28.3 (MR !11334, commit 48c11b7b01). Reported via PSIRTSUPT-7239 by Tianshuo Han.

GStreamer H.266/VVC PPS picture partition parser out-of-bounds write. In gsth266parserparsepicturepartition(), the multi-slice-in-tile loop writes past fixed-size arrays without bounds checking. Fixed in GStreamer 1.28.3 (commit f66e8292ed, MR !11581). Reported via PSIRTSUPT-7239 by Tianshuo Han.

Localsearch improved their sandbox a few years ago to address CVE-2023-5557. Previously, the main thread wasn't as strictly sandboxed as the worker threads, which is how my poc for CVE-2023-43641 was able to break out of the sandbox. But their new seccomp sandbox looks extremely strong to me. If I remember correctly, they've made it so that the process that parses the untrusted files cannot even send arbitrary D-Bus messages. It's restricted to only communicating with it's parent process, using a very limited protocol. Last time I looked, I concluded that a sandbox escape would be hopeless. There are probably other applications that use gstreamer which are softer targets though.

Kev

On Fri, 1 May 2026, 08:38 Demi Marie Obenour, <demiobenour () gmail com> wrote: On 4/30/26 19:59, Solar Designer wrote: Hi, The GStreamer library is used to parse multimedia files in Nautilus (GNOME Files), GNOME Videos, and Rhythmbox, as well as in the localsearch search engine (previously known as tracker-miners) developed by the GNOME project. This engine is installed in many distributions as a dependency of the tracker-extract package, which GNOME uses to automatically parse metadata in new files. Among other things, this service indexes all files in the user's home directory without any user interaction. Therefore, to perform an attack, simply create a specially crafted multimedia file in the user's home directory, and the vulnerability will be exploited during its automatic indexing.

In most GNOME distributions, localsearch components (tracker-miners) are enabled by default and loaded as a hard dependency of the Nautilus file manager (GNOME Files). Starting with GNOME 46, the localsearch process runs in sandbox isolation. To disable metadata extraction, you can delete the rules files from the /usr/share/localsearch3/extract-rules/ or /usr/share/tracker3-miners/extract-rules/ directory. I don't know how good or not the mentioned "sandbox isolation" is, I'd welcome comments on the risks involved and potential further hardening.

Alexander Last I checked, the sandbox was not very good. In particular, there were seccomp rules that were thread-scoped rather than process-scoped, allowing for sandbox escape. It might have improved, though.

My current opinion is that it is possible to create a truly strong sandbox on Linux that is nearly as good as hardware virtualization. However, doing so requires severely limiting the number of system calls available. The attack surface is then mostly limited to memory management, which KVM also has to some degree. -- Sincerely, Demi Marie Obenour (she/her/hers)

On 4/30/26 19:59, Solar Designer wrote: Hi, The GStreamer library is used to parse multimedia files in Nautilus (GNOME Files), GNOME Videos, and Rhythmbox, as well as in the localsearch search engine (previously known as tracker-miners) developed by the GNOME project. This engine is installed in many distributions as a dependency of the tracker-extract package, which GNOME uses to automatically parse metadata in new files. Among other things, this service indexes all files in the user's home directory without any user interaction. Therefore, to perform an attack, simply create a specially crafted multimedia file in the user's home directory, and the vulnerability will be exploited during its automatic indexing.

In most GNOME distributions, localsearch components (tracker-miners) are enabled by default and loaded as a hard dependency of the Nautilus file manager (GNOME Files). Starting with GNOME 46, the localsearch process runs in sandbox isolation. To disable metadata extraction, you can delete the rules files from the /usr/share/localsearch3/extract-rules/ or /usr/share/tracker3-miners/extract-rules/ directory. I don't know how good or not the mentioned "sandbox isolation" is, I'd welcome comments on the risks involved and potential further hardening.

Alexander Last I checked, the sandbox was not very good. In particular, there were seccomp rules that were thread-scoped rather than process-scoped, allowing for sandbox escape. It might have improved, though.

My current opinion is that it is possible to create a truly strong sandbox on Linux that is nearly as good as hardware virtualization. However, doing so requires severely limiting the number of system calls available. The attack surface is then mostly limited to memory management, which KVM also has to some degree. -- Sincerely, Demi Marie Obenour (she/her/hers)

Hi,

I brought a bunch of GStreamer CVEs in here in March. In April, there was a new release with more CVEs announced/fixed. I'd really rather not be the one to be taking care of this - I guess we have subscribers who are involved with the project or its packaging? Anyone, please?

The new release is "1.28.2 stable bug fix release" with website news item dated "2026-04-07 23:00" and said to include "Various security fixes" and a lot more (with specifics). The security fixes are for: GStreamer-SA-2026-0023 Denial of service in SRT/WebVTT parser 2026-04-07 23:59

GStreamer-SA-2026-0022 CVE-2026-pending Heap buffer overflow in Matroska demuxer 2026-04-07 23:59

GStreamer-SA-2026-0021 CVE-2026-pending Integer overflow in WAV parser cue handling 2026-04-07 23:59

GStreamer-SA-2026-0020 Assertion failures in FLV demuxer on corrupted streams 2026-04-07 23:59

GStreamer-SA-2026-0019 NULL-pointer dereferences in mDVDsub subtitle parser 2026-04-07 23:59

GStreamer-SA-2026-0018 CVE-2026-pending MOV/MP4 demuxer audio channel parsing vulnerabilities 2026-04-07 23:59

GStreamer-SA-2026-0017 Integer overflow in H.266/VVC parser leading to stack overflow 2026-04-07 23:59

GStreamer-SA-2026-0016 CVE-2026-5056 ZDI-CAN-29392 Integer overflows and out-of-bounds access in MOV/MP4 demuxer 2026-04-07 23:59

GStreamer-SA-2026-0015 CVE-2026-pending Integer overflows in JPEG 2000 decimator 2026-04-07 23:59

GStreamer-SA-2026-0014 Integer overflow in AV1 LEB128 parser 2026-04-07 23:59

GStreamer-SA-2026-0013 H.264 video parser NULL pointer dereference when freeing SPS/MVC data 2026-04-07 23:59 as listed at https://gstreamer.freedesktop.org/security/ along with links to "Details" for each (which I have no time to extract and process into this posting).

On Mon, Mar 16, 2026 at 03:58:16AM +0100, Solar Designer wrote: The news story at:

https://www.opennet.me/opennews/art.shtml?num=64964

originally in Russian explains GStreamer usage as follows, translated to English here: The GStreamer library is used to parse multimedia files in Nautilus (GNOME Files), GNOME Videos, and Rhythmbox, as well as in the localsearch search engine (previously known as tracker-miners) developed by the GNOME project. This engine is installed in many distributions as a dependency of the tracker-extract package, which GNOME uses to automatically parse metadata in new files. Among other things, this service indexes all files in the user's home directory without any user interaction. Therefore, to perform an attack, simply create a specially crafted multimedia file in the user's home directory, and the vulnerability will be exploited during its automatic indexing.

In most GNOME distributions, localsearch components (tracker-miners) are enabled by default and loaded as a hard dependency of the Nautilus file manager (GNOME Files). Starting with GNOME 46, the localsearch process runs in sandbox isolation. To disable metadata extraction, you can delete the rules files from the /usr/share/localsearch3/extract-rules/ or /usr/share/tracker3-miners/extract-rules/ directory. I don't know how good or not the mentioned "sandbox isolation" is, I'd welcome comments on the risks involved and potential further hardening.

Alexander

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 parsing of UncompressedFrameConfigBox structures. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process.