# CVE-2026-121611: A flaw was found in GStreamer's gst-plugins-bad package.


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-121611, ECHO-1500-ee37-81e1, GHSA-m394-f7p9-g5gg, UBUNTU-CVE-2026-121611

## What is CVE-2026-121611?

CVE-2026-121611 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 gst-plugins-bad package. A use of uninitialized memory vulnerability exists in the H.265 (HEVC) bitstream parser when processing Video Parameter Sets that declare more than one HRD (Hypothetical Reference Decoder) parameter set. A remote attacker could exploit this by providing a crafted H.265 media file or stream that, when processed by an application using GStreamer, causes unpredictable parser behavior and may crash the application. This can lead to a denial of service for any application using GStreamer to play back H.265 content.

Weakness: CWE-457 (Use of Uninitialized Variable)

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


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

Upgrade to a fixed version.

## Is CVE-2026-121611 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121611 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-121611 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-121611/ (Markdown: https://insights.sbomify.com/CVE-2026-121611/index.md)
```

## Sources

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

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