# CVE-2026-121601: A flaw was found in GStreamer's MXF demuxer plugin (gst-plugins-bad).


- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-121601, ECHO-5608-88d5-019e, GHSA-pwwr-87p6-hjj7, UBUNTU-CVE-2026-121601

## What is CVE-2026-121601?

CVE-2026-121601 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 9 Nov 2026. 

### Official description

A flaw was found in GStreamer's MXF demuxer plugin (gst-plugins-bad). When processing a specially crafted MXF media file, the demuxer indexes its internal delta-entry and slice-offset tables using values from the file without validating that they are within the bounds of the allocated arrays. A local attacker who tricks a user into opening a malicious MXF file can cause the application to crash (denial of service) and may be able to read limited amounts of heap memory adjacent to the affected arrays.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-121601 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121601 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121601 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-121601/ (Markdown: https://insights.sbomify.com/CVE-2026-121601/index.md)
```

## Sources

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

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