CVE-2026-53703
Awaiting Analysis Awaiting Analysis - Queue
GStreamer RealMedia Demuxer Buffer Overflow

Publication date: 2026-06-15

Last updated on: 2026-06-15

Assigner: Red Hat, Inc.

Description
A vulnerability was found in the GStreamer RealMedia demuxer (gst-plugins-ugly). When processing a RealMedia (.rm) file, the demuxer parses MDPR (media properties) chunks to configure audio streams. For audio stream header versions 4 and 5, the parser reads fields such as codec type, packet size, sample rate, channel count, and extra codec data length from fixed offsets within the chunk without first checking that the chunk contains enough data. If a malicious file provides an MDPR chunk that is too small to contain a complete audio stream header, the parser reads beyond the end of the buffer. This can cause the application to crash. In some cases, bytes read past the buffer boundary may be incorporated into stream metadata, which could result in limited information disclosure.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-15
Last Modified
2026-06-15
Generated
2026-06-16
AI Q&A
2026-06-15
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
gst-plugins-ugly gstreamer1-plugins-ugly-free *
gstreamer gst-plugins-ugly *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-125 The product reads data past the end, or before the beginning, of the intended buffer.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in the GStreamer RealMedia demuxer component, specifically in the gst-plugins-ugly package. When processing RealMedia (.rm) files, the demuxer parses MDPR chunks to configure audio streams. For audio stream header versions 4 and 5, the parser reads codec parameters from fixed byte offsets without verifying that the chunk contains enough data. If a malicious file provides an MDPR chunk that is too small, the parser reads beyond the buffer boundary, causing an out-of-bounds read.

This out-of-bounds read can cause the application to crash or, in some cases, incorporate unintended bytes into stream metadata, potentially leading to limited information disclosure.

Impact Analysis

The vulnerability can cause applications using the affected GStreamer RealMedia demuxer to crash due to out-of-bounds memory reads. This can lead to denial of service if the application is critical or widely used.

Additionally, in some cases, the out-of-bounds read may result in limited information disclosure by incorporating unintended bytes into stream metadata, which could potentially expose sensitive information.

Detection Guidance

This vulnerability involves an out-of-bounds read in the GStreamer RealMedia demuxer when processing malformed RealMedia (.rm) files. Detection would involve identifying attempts to process such malicious .rm files that trigger crashes or abnormal behavior in applications using the vulnerable gst-plugins-ugly component.

Since the issue occurs during parsing of MDPR chunks in RealMedia files, monitoring for application crashes or logs related to gst_rmdemux_parse_mdpr() failures could help detect exploitation attempts.

No specific detection commands or signatures are provided in the available resources.

Mitigation Strategies

As of the current information, no fix is available for this vulnerability. Upstream developers recommend a complete rewrite of the rmdemux component to address the issue.

Immediate mitigation steps include avoiding the use or processing of untrusted RealMedia (.rm) files with applications that use the vulnerable gst-plugins-ugly package.

Monitoring for crashes or abnormal behavior in applications using the RealMedia demuxer and restricting access to potentially malicious media files can reduce risk.

Compliance Impact

The vulnerability can cause limited information disclosure by incorporating bytes read past the buffer boundary into stream metadata. This limited information disclosure could potentially impact compliance with data protection regulations such as GDPR or HIPAA, which require safeguarding personal and sensitive information. However, the provided information does not specify any direct or explicit impact on compliance with these standards.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-53703. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart