Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-18649: Unbounded RTP Reassembly Memory Consumption in GStreamer gst-plugins-good

Published Aug 6, 2026 · Updated 7 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 1 in a dayToday
CVSS7.5High · v3.1
EPSS0.96%62nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-18649CWE-770 · Allocation of Resources Without…

CVE-2026-18649 is a resource-exhaustion vulnerability in the rtph264depay and rtph265depay RTP depayloader elements of GStreamer gst-plugins-good. These elements do not enforce a maximum reassembly-buffer size when processing fragmented H.264 or H.265 RTP packets. A remote, unauthenticated attacker can continuously submit fragments without an end-of-fragment marker, causing the buffer to grow until process memory is exhausted and the affected process terminates.

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 causes excessive memory consumption and denial of service through termination of the application processing the RTP stream. The vulnerability has a CVSS v3.0 base score of 7.5, with high availability impact and no identified confidentiality or integrity impact.

Mitigation

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

Until patched, restrict untrusted RTP sources from reaching applications using the affected depayloaders through network filtering and segmentation. Apply packet validation, network-level rate limiting, and process memory limits as defense-in-depth measures. Rate limiting can slow memory exhaustion but does not correct the unbounded buffer growth, and process resource limits do not prevent application-level denial of service.

Remediation

Patch, then assume compromise.

Install the vendor-provided security update for gst-plugins-good and associated distribution packages. Ubuntu systems should apply USN-8778-1; the listed Ubuntu 16.04, 18.04, and 20.04 ESM fixes require Ubuntu Pro. RHEL systems should apply the advisory matching their release and support stream. Echo packages should be updated to 1.26.2-1+e8 or later. Fedora MinGW advisories prescribe GStreamer 1.28.8; the Fedora 45 1.28.8-1.fc45 builds are identified as pending testing and not yet published to stable.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

View more in app →
CVE-2026-18649This repository is a small standalone proof-of-concept for CVE-2026-18649, a remote denial-of-service issue in GStreamer's H.264 RTP depayloader (rtph264depay), with the README noting the same pattern also affects rtph265depay. The repository contains three files: a README describing the vulnerability, impact, and usage; a minimal requirements.txt stating only Python standard library and GStreamer prerequisites; and the main exploit script trigger.py. The exploit logic in trigger.py is straightforward and purpose-built. It creates a UDP socket and sends crafted RTP packets to a target port on 127.0.0.1. It first sends a valid H.264 FU-A start fragment, then continuously sends continuation fragments while never setting the FU end bit. Sequence numbers are incremented to keep packets looking valid. This causes the target depayloader to keep appending fragment data into its internal reassembly buffer without flushing, resulting in unbounded heap growth. The script optionally accepts a PID and monitors /proc/<pid>/status to report VmData growth and detect when the target process dies. The exploit is a real DoS exploit rather than a detector. It does not provide code execution or shell access; its sole capability is remote resource exhaustion against a vulnerable RTP-processing pipeline. The PoC is local by default because it targets 127.0.0.1, but the underlying vulnerability is network-reachable anywhere a vulnerable GStreamer RTP receiver is exposed. The code is concise, uses only Python's standard library, and is best classified as a proof-of-concept.0xSemizzz · Disclosed Aug 6, 2026 · python · markdown · networkPoCcve-2026-18649The repository contains a standalone, incomplete containerized denial-of-service proof of concept: one Python packet generator, two Dockerfiles, a Compose configuration, and a .gitignore excluding .env. No exploit framework, CVE identifier, affected release range, or verified vulnerable commit is supplied. sender/send_rtp.py uses Python's standard library to transmit malformed H.264 FU-A fragments over UDP. It sends one start fragment followed by continuation fragments, never setting the end bit or changing the RTP timestamp. The default run lasts approximately 20 seconds and sends about 10 MB of fragment data. Packet count, destination, and port are configurable; the transmission rate is fixed at approximately 500 packets per second. This is intended to exercise incomplete-fragment buffering rather than execute code. Whether it produces meaningful memory growth depends on the target implementation; the code does not measure or confirm that outcome. receiver/Dockerfile builds a user-selected GStreamer revision on Ubuntu 24.04 and launches an H.264 RTP pipeline ending in rtph264depay and fakesink. Compose specifies a 512 MB receiver memory limit and an internal network, with UDP port 5000 exposed only to the container network rather than published to the host. The supplied lab is not runnable unchanged. Compose defines a builder service whose ./builder directory is absent, depends on a misspelled and undefined reciever service, and omits the actual sender service. Additionally, disabling automatic GStreamer features while enabling RTP but not the UDP plugin may leave the required udpsrc element unavailable. These limitations make this an unverified PoC rather than a demonstrated operational exploit. There are no apparent destructive local commands or concealed callbacks; the source-download URL is used only during the build. Original repository URL, analyzed Git reference, and archive size were not provided; their metadata fields use empty or zero placeholders.C3viche · Disclosed Oct 31, 2026 · python · dockerfile · networkPoC
FAQ

Frequently asked questions

Is CVE-2026-18649 exploited in the wild?
As of Nov 10, 2026, Mallory has no reports of CVE-2026-18649 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-18649?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2026-18649, the earliest disclosed Aug 6, 2026.
Is there a patch for CVE-2026-18649?
Install the vendor-provided security update for gst-plugins-good and associated distribution packages. Ubuntu systems should apply USN-8778-1; the listed Ubuntu 16.04, 18.04, and 20.04 ESM fixes require Ubuntu Pro.
How severe is CVE-2026-18649?
CVE-2026-18649 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.96% (62nd percentile) as of Nov 10, 2026.
Activity feed

Recent activity

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

View more in app →
tenable nessus pluginsNews · Nov 9, 2026CentOS Linux 7 [TuxCare] Security Update: gstreamer1-plugins-g... | Tenable®An unauthenticated remote attacker can exhaust process memory by continuously sending RTP fragments without an end-of-fragment marker, causing process termination and denial of service. The advisory-level plugin reports exploits are available but does not identify which listed vulnerability that applies to.Read more ↗tenable nessus pluginsNews · Nov 4, 2026TencentOS Server 2: gstreamer1-plugins-good (TSSA-2026:1358) | Tenable®An unbounded memory-consumption vulnerability in GStreamer gst-plugins-good allows an unauthenticated remote attacker to exhaust process memory by continuously sending RTP fragments without an end-of-fragment marker, causing process termination and denial of service. TencentOS Server 2 package updates are available. The plugin reports exploit availability collectively but does not identify which CVEs have exploits.Read more ↗tenable nessus pluginsNews · Oct 31, 2026Fedora 45 : mingw-gstreamer1 / mingw-gstreamer1-plugins-bad-fr... | Tenable®One of five vulnerabilities covered by a Fedora 45 security update for MinGW GStreamer packages. The content does not describe this CVE's specific flaw or impact. Nessus checks self-reported package versions rather than testing exploitation. Exploit availability is reported for the advisory collectively, without identifying this CVE specifically.Read more ↗tenable nessus pluginsNews · Oct 28, 2026Fedora 44 : mingw-gstreamer1 / mingw-gstreamer1-plugins-bad-fr... | Tenable®A vulnerability covered by a security update for Fedora 44 MinGW GStreamer packages. The reference does not describe its technical mechanism or individual impact. Nessus checks self-reported package versions rather than testing exploitation.Read more ↗
+27 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 activity2Community discussion across Reddit, Mastodon, and other social sources.