# CVE-2026-119610: A flaw was found in GStreamer's gst-plugins-good, specifically in the H.264 RTP depayloader element.


- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-119610, ECHO-513c-a776-2a1f, GHSA-3mhh-mxj4-9x34, UBUNTU-CVE-2026-119610

## What is CVE-2026-119610?

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

### Official description

A flaw was found in GStreamer's gst-plugins-good, specifically in the H.264 RTP depayloader element. When processing MTAP16 or MTAP24 multi-time aggregation RTP packets, a signed/unsigned integer conversion error causes the remaining-length counter to underflow to a large positive value when the packet is truncated. This allows a remote, unauthenticated attacker to trigger an out-of-bounds heap read of up to approximately 64 KiB of process memory by sending a single malformed RTP packet. Successful exploitation can crash the receiving GStreamer pipeline (denial of service), and in relay or transcoding deployments where output is accessible to the attacker, may expose adjacent heap contents.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-119610 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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