# CVE-2026-119728: Gst-plugins-bad: gst-plugins-bad: null pointer dereference in h.264 mvc sps cleanup during parse failure


- **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:** 30 Oct 2026
- **Updated:** 5 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-119728, ECHO-f74f-ca87-b65b, GHSA-r374-jvgj-7922, UBUNTU-CVE-2026-119728

## What is CVE-2026-119728?

CVE-2026-119728 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 30 Oct 2026. 

### Official description

A flaw was found in the H.264 video parser in gst-plugins-bad. When processing a specially crafted H.264 video file or network stream with malformed Multiview (MVC) Sequence Parameter Set data, the parser can dereference a NULL pointer during the cleanup of partially allocated internal structures after a parse failure. This can cause the application using GStreamer to crash, resulting in a denial of service.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

Upgrade to a fixed version.

## Is CVE-2026-119728 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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