# CVE-2026-52721: Gstreamer1-plugins-bad-free: gstreamer: multiple out-of-bounds reads in pcapparse ipv4/tcp header parsing

> A local attacker can cause crashes or leak memory by tricking a user into opening a malicious PCAP file in GStreamer's pcapparse element.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-52721, ECHO-3756-c3c5-31e0, GHSA-9qf3-vv3w-6xw5, UBUNTU-CVE-2026-52721

## What is CVE-2026-52721?

CVE-2026-52721 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 15 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-52721?


## How do I fix CVE-2026-52721?

Apply the vendor's patch.

## Is CVE-2026-52721 being exploited?

There is no known exploitation of CVE-2026-52721 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-52721 and fix it if it is affected.

What it is: CVE-2026-52721 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 15 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-52721 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-52721/ (Markdown: https://insights.sbomify.com/CVE-2026-52721/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-52721
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-52721
- OSV: https://osv.dev/vulnerability/CVE-2026-52721

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-52721/
Summaries are generated and may contain mistakes; the official description above is the record.
