On this page (7 sections)

Ubuntu published security notice USN-9038-1 on 2026-11-10 for GStreamer Good Plugins. It covers several flaws in how the media framework handles network streams and files. Two of them, CVE-2026-3083 and CVE-2026-3085, sit in the RTP depayloader for the X-QDM audio format and are rated high severity (CVSS 8.8) with possible code execution.

If you run Ubuntu 16.04 LTS, 18.04 LTS or 20.04 LTS servers or workstations that process media (transcoding, thumbnails, streaming, video conferencing back ends), this notice is for you. Plain web servers that never touch GStreamer are far less likely to be exposed, but it is worth confirming rather than assuming.

What the notice covers

Ubuntu says GStreamer Good Plugins did not properly handle certain network streams, and that a remote attacker could possibly cause an application crash or execute arbitrary code. That item maps to CVE-2026-3083 and CVE-2026-3085. The same notice lists further problems in the Good Plugins package: a Matroska file handling bug (CVE-2026-39043), a WAV file bug (CVE-2026-39044) and an MP4 audio track bug. Ubuntu describes those three as leading to a crash and denial of service. The notice text available to us is cut off after the MP4 item, so there may be more entries than we can list here.

Ubuntu states these issues only affected Ubuntu 16.04 LTS, 18.04 LTS and 20.04 LTS. Those are older releases, so it is worth checking which of your systems still run them and whether an upgrade is due.

CVE-2026-39043 had no NVD record at the time of writing, so no CVSS score or CWE is available for it. The only description we have is Ubuntu's: a crash and denial of service from certain Matroska files.

Technical details of the two RTP flaws

Both bugs are in rtpqdm2depay, the component that unpacks X-QDM audio carried over RTP (a common transport for live audio and video streams). Both were reported through the Zero Day Initiative as ZDI-26-166 and ZDI-26-167.

The two high-severity GStreamer RTP flaws
CVEWeaknessWhat goes wrongCVSS
CVE-2026-3083CWE-129, CWE-787 (out-of-bounds write)The packetid element is not validated, so a write can land past the end of an allocated array8.8
CVE-2026-3085CWE-122, CWE-1284 (heap overflow)The length of user-supplied data is not validated before it is copied into a heap buffer8.8

In plain terms, the parser trusts numbers inside the stream (an index in one case, a length in the other) without checking them against the size of the memory it is about to write to. A crafted stream can then overwrite adjacent memory, which in the worst case lets an attacker run code with the privileges of the process that is decoding the stream.

The GitHub advisory entries give the vector as CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. That means network reachable, low complexity, no privileges, but user interaction required. The advisories add that interaction with the library is needed and attack vectors may vary by implementation. In practice this means an application must actually open or ingest the hostile stream.

The GitHub entries show EPSS estimates of 0.949% for CVE-2026-3083 and 1.564% for CVE-2026-3085 (probability of exploitation within 30 days, per FIRST). These are low but not zero, and neither CVE appears in CISA's KEV data we reviewed. We found no public report of exploitation.

Who is realistically exposed

GStreamer is a library, not a daemon, so exposure depends on which applications link against it. Think about:

  • Media pipelines that ingest RTP or RTSP streams from outside your network.
  • Services that generate thumbnails, previews or transcodes of user-uploaded audio and video.
  • Desktop-style tools on servers or admin workstations that open untrusted media files.
  • Containers or build images based on Ubuntu 16.04, 18.04 or 20.04 that include GStreamer packages.

A typical brochure website or WordPress host with no media processing on the server is unlikely to use these code paths. The Matroska, WAV and MP4 issues, per Ubuntu, lead to crashes, so the main risk there is a denial of service for whatever service handles those files.

How to check your exposure

First confirm your Ubuntu release. The command is read-only and prints the release name and version.

Show the Ubuntu release (run on each host)Shell
lsb_release -a

Then list installed GStreamer packages and their versions. Any output means the library is present; compare the versions with those in the USN-9038-1 page for your release.

List installed GStreamer packages (Debian/Ubuntu)Shell
dpkg -l | grep -i gstreamer

To see which running services might be using it, look for processes that have GStreamer libraries loaded. This only reads process information; run it as root to see all processes.

Find running processes that map GStreamer librariesShell
grep -l libgst /proc/[0-9]*/maps 2>/dev/null

What to do now

  1. Inventory hosts and container images on Ubuntu 16.04, 18.04 and 20.04, and note which have GStreamer packages installed.
  2. Read USN-9038-1 and confirm the fixed package versions for your release.
  3. Update the packages with your normal process (commands below), then restart services that use GStreamer.
  4. Rebuild container images from updated bases rather than patching running containers only.
  5. If you cannot patch yet, avoid feeding untrusted RTP streams and media files to GStreamer-based services and run them with minimal privileges.
  6. Check the support status of each Ubuntu release you run and plan upgrades for older systems.

This refreshes the package index and upgrades installed packages on Debian/Ubuntu. Review what it will change on production hosts first.

Update packages on Ubuntu (run as root or with sudo)Shell
sudo apt update
sudo apt upgrade
Caution. Upgrading shared libraries does not affect programs that are already running. Restart the services that use GStreamer (or reboot in a maintenance window) so they load the fixed code, and expect brief interruption to media features.

Red Hat has also published errata for CVE-2026-3083 and CVE-2026-3085 (for example RHSA-2026:7850), so RHEL-family systems with GStreamer should be checked against Red Hat's own advisories. Fixed package versions are not given in the research, so use the errata for your release.

Detection and monitoring afterwards

Because the likely symptom of failed exploitation is a crash, watch for unexpected restarts or segmentation faults in media-handling services. Checking recent kernel and service logs is a read-only way to spot this.

Search the system log for recent crashes (Debian/Ubuntu)Shell
journalctl -k --since "7 days ago" | grep -i segfault

Repeated crashes of a transcoding or streaming service shortly after it handled outside content deserve a closer look at the input that triggered them. Keep package update checks on a schedule so library fixes reach servers that nobody thinks of as media hosts. For web-facing systems, Webforta Monitor can alert you to certificate, DNS and header changes, and the guide on what to do if a website is hacked covers response steps if you suspect compromise.

What we could not confirm

  • The exact fixed package versions: the Ubuntu notice text we had was truncated.
  • The contents of the upstream fix: the GStreamer commit page referenced by the CVE records did not load for us, so we do not describe the patch.
  • Any severity rating for CVE-2026-39043, which had no NVD record yet.
  • Whether other Ubuntu releases or other distributions are affected beyond what Ubuntu and Red Hat list.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-3083 - GitHub Advisory Databasegithub.com
  2. Making sure you're not a bot!gitlab.freedesktop.org
  3. CVE-2026-3085 - GitHub Advisory Databasegithub.com
  4. USN-9038-1: GStreamer Good Plugins, GStreamer Base Plugins vulnerabilitiesubuntu.com ·
  • GStreamer
  • Ubuntu
  • USN-9038-1
  • Linux
  • Patch management