Quick answers
- Is CVE-2026-92475 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92475 being exploited in the wild.
- How severe is CVE-2026-92475?
- Medium severity, with a CVSS score of 5.3, published 16 September 2026.
- Which products and versions are affected?
- Gpac 26.08-DEV and earlier; fixed in abi-16.26.
- Is there a fix for CVE-2026-92475?
- A patch was published on 2026-09-16: Patch c74a3065038ede35c1c7b75fa493a69ef6bcdb84 available for version abi-16.26 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92475 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-92475?
- 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
This vulnerability is an out-of-bounds read in the wait_for_header_and_parse function located in src/utils/downloader.c. The root cause is improper validation of the Content-Range HTTP header argument, which can be manipulated to read memory beyond allocated boundaries. The attack vector requires local access to the system. An attacker can exploit this to leak sensitive information from memory or cause a denial of service through application crash. The issue has been fixed in version abi-16.26 (patch c74a3065038ede35c1c7b75fa493a69ef6bcdb84), which corrects the strchr pattern handling that was leading to heap overflows.
Affected products
- GPAC GPAC 26.08-DEV and earlier; fixed in abi-16.26
Timeline
- 2026-09-16: disclosed
- 2026-09-16: patched: Patch c74a3065038ede35c1c7b75fa493a69ef6bcdb84 available for version abi-16.26