Quick answers
- Is CVE-2026-93331 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93331 being exploited in the wild.
- How severe is CVE-2026-93331?
- High severity, with a CVSS score of 7.3, published 18 September 2026.
- Which products and versions are affected?
- Gpac 26.08-DEV.
- Is there a fix for CVE-2026-93331?
- A patch was published on 2026-09-18: Patch 6bb0f64b4d1039c0fecd14ee2c1ee861d8661a68 available in version abi-16.26 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93331 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-93331?
- Check whether you run Gpac at an affected version. 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.
Technical details
An out-of-bounds read vulnerability exists in the gf_rtp_parse_ttxt() function of the RTP depacketizer component (src/ietf/rtp_depacketizer.c). The vulnerability arises from insufficient validation of the advertised payload size against the actual buffer size, allowing an attacker to read beyond allocated memory. The attack is network-based and does not require authentication or user interaction—a malicious RTP packet triggers the vulnerability. An attacker can read arbitrary memory, potentially leaking sensitive data or causing information disclosure. The fix validates the advertised size against the actual buffer before processing, implemented in patch 6bb0f64b4d1039c0fecd14ee2c1ee861d8661a68 and available in version abi-16.26.
Affected products
- GPAC GPAC 26.08-DEV
Timeline
- 2026-09-18: disclosed
- 2026-09-18: patched: Patch 6bb0f64b4d1039c0fecd14ee2c1ee861d8661a68 available in version abi-16.26