Quick answers
- Is CVE-2026-111183 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111183 being exploited in the wild.
- How severe is CVE-2026-111183?
- Critical severity, with a CVSS score of 9.8, published 21 October 2026.
- Which products and versions are affected?
- GStreamer GStreamer.
- Is there a fix for CVE-2026-111183?
- Yes: fixed in The fix was committed on Oct 08, 2026 (commit 80c184b4); check GStreamer releases after this date for patched versions.. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111183 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111183?
- Check whether you run Gstreamer. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: The fix was committed on Oct 08, 2026 (commit 80c184b4); check GStreamer releases after this date for patched versions.
Technical details
The vulnerability exists in the rtpL16depay, rtpL8depay, and rtpL24depay RTP depayloaders, which fail to bounds-check the channel count signaled in SDP before writing to a fixed 64-entry positions array. An attacker can craft an RTP stream with an abnormally high channel count to write beyond the array bounds. The attack is network-accessible with no authentication or user interaction required, and successful exploitation results in arbitrary code execution in the context of the library's process.
Affected products
- GStreamer GStreamer
Timeline
- 2026-08-20: disclosed: Vulnerability reported to vendor
- 2026-10-08: patched: Fix committed to GStreamer repository (commit 80c184b4)
- 2026-10-15: advisory: ZDI coordinated public disclosure