CVE-2026-52721
Awaiting Analysis Awaiting Analysis - Queue
Out-of-Bounds Read in GStreamer pcapparse Element

Publication date: 2026-06-15

Last updated on: 2026-06-15

Assigner: Red Hat, Inc.

Description
Multiple out-of-bounds read vulnerabilities were found in GStreamer's pcapparse element. Malformed PCAP records can trigger reads beyond buffer boundaries during IPv4/TCP header parsing. This element is primarily used in debugging pipelines, limiting real-world exposure. A local attacker could trick a user into processing a specially crafted PCAP file, potentially leading to a crash or 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 3 associated CPEs
Vendor Product Version / Range
gnome gstreamer 1.28.4
gnome gstreamer1-plugins-bad-free to 1.28.4 (inc)
gnome gstreamer *
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 involves multiple out-of-bounds read issues in the pcapparse element of GStreamer, specifically in the IPv4/TCP header parsing logic. When processing malformed PCAP records, the code reads data beyond the buffer boundaries because it does not properly verify that enough data exists after the IP header for TCP/UDP fields. Additionally, the payload size calculation trusts the IP packet length field, which can be spoofed to exceed the actual buffer size, causing reads from adjacent PCAP records.

The pcapparse element is mainly used in debugging pipelines, which limits the chances of this vulnerability being exploited in real-world scenarios.

Impact Analysis

A local attacker could trick a user into processing a specially crafted PCAP file that triggers these out-of-bounds reads. This could potentially lead to a crash of the application or disclosure of information from adjacent memory areas.

However, since the vulnerable element is primarily used in debugging pipelines, the likelihood of real-world exploitation is very low.

Detection Guidance

This vulnerability occurs in the GStreamer pcapparse element when processing specially crafted PCAP files in debugging pipelines. Detection involves identifying usage of vulnerable GStreamer versions with the pcapparse element and monitoring for crashes or abnormal behavior when processing PCAP files.

Since the vulnerability is triggered by malformed PCAP files, you can check for the presence of the vulnerable gstreamer1-plugins-bad-free package and its version.

Suggested commands to detect the vulnerability or its exploitation attempts include:

  • Check installed GStreamer plugins and versions: `gst-inspect-1.0 pcapparse`
  • Verify package version (example for RPM-based systems): `rpm -q gstreamer1-plugins-bad-free`
  • Monitor system logs for crashes or errors related to GStreamer or pcapparse.
  • Use file inspection tools to identify suspicious or malformed PCAP files that might trigger the vulnerability.
Mitigation Strategies

Immediate mitigation steps include avoiding the use of the vulnerable pcapparse element in GStreamer pipelines, especially for processing untrusted PCAP files.

Update the gstreamer1-plugins-bad-free package to version 1.28.4 or later once the fix is released, as this version will contain the patch for the out-of-bounds read vulnerabilities.

Limit user interaction with untrusted PCAP files and avoid processing such files in debugging pipelines that use the pcapparse element.

Implement monitoring for crashes or abnormal behavior in applications using GStreamer with the pcapparse element.

Compliance Impact

The vulnerability in GStreamer's pcapparse element could potentially lead to information disclosure if a user processes a specially crafted PCAP file. Such information disclosure risks may have implications for compliance with data protection standards like GDPR or HIPAA, which require safeguarding sensitive information.

However, the element is primarily used in debugging pipelines, limiting real-world exposure, and the attack requires local user interaction with a crafted file. Therefore, the practical impact on compliance with these regulations is likely minimal but should be considered in environments where sensitive data is processed using vulnerable versions.

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