# CVE-2026-111183: GStreamer rtpL16depay Heap-based Buffer Overflow Remote Code Execution Vulnerability


- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-111183, ECHO-72a0-7caf-d131, GHSA-62fg-53h6-6f68, UBUNTU-CVE-2026-111183

## What is CVE-2026-111183?

CVE-2026-111183 is a critical vulnerability in GStreamer, published on 21 Oct 2026. 

### Official description

GStreamer rtpL16depay Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. Interaction with this library is required to exploit this vulnerability but attack vectors may vary depending on the implementation.

The specific flaw exists within the processing of RTP payload elements. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-31143.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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


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

Upgrade to a fixed version.

## Is CVE-2026-111183 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111183 is a critical vulnerability in GStreamer, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-111183 in the wild and no public exploit code.

Affected product: GStreamer. 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-111183/ (Markdown: https://insights.sbomify.com/CVE-2026-111183/index.md)
```

## Sources

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

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