Quick answers
- Is CVE-2026-91088 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-91088 being exploited in the wild.
- How severe is CVE-2026-91088?
- Medium severity, with a CVSS score of 4.8, published 15 September 2026.
- Which products and versions are affected?
- Gpac up to f1219cde.
- Is there a fix for CVE-2026-91088?
- A patch was published on 2026-07-27: Patch commit afca1f1181668d85941d51ed1adf647807d5d975 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-91088 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-91088?
- 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
A heap-based buffer overflow exists in the gf_url_concatenate_ex function in utils/url.c of the URL Handler component in GPAC up to commit f1219cde. The vulnerability stems from improper bounds checking when concatenating URL strings. The attack vector is local; an attacker must provide a malicious input locally (not remotely exploitable). Successful exploitation could lead to denial of service via crash or potentially arbitrary code execution. The vulnerability has been patched in version abi-16.23 with commit afca1f1181668d85941d51ed1adf647807d5d975.
Affected products
- GPAC GPAC up to f1219cde
Timeline
- 2026-09-15: disclosed
- 2026-07-27: patched: Patch commit afca1f1181668d85941d51ed1adf647807d5d975