Quick answers
- Is CVE-2026-92474 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92474 being exploited in the wild.
- How severe is CVE-2026-92474?
- Low severity, with a CVSS score of 3.3, published 16 September 2026.
- Which products and versions are affected?
- Gpac 26.08-DEV.
- Is there a fix for CVE-2026-92474?
- A patch was published on 2026-08-03: Commit e34f4ba349d55cd1849f0bcf4cf46552732e2db7 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92474 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-92474?
- 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 use-after-free vulnerability exists in the gf_inline_get_proto_lib function within src/compositor/mpeg4_inline.c of GPAC's Proto Link Handler component. The flaw results from improper memory management where a pointer is dereferenced after the object it points to has been freed. The vulnerability requires local access and can be triggered through crafted GPAC media files. An attacker exploiting this issue can cause a denial-of-service crash. A patch is available in commit e34f4ba349d55cd1849f0bcf4cf46552732e2db7, and upgrading to version abi-16.24 or later mitigates the issue.
Affected products
- GPAC GPAC 26.08-DEV
Timeline
- 2026-09-16: disclosed
- 2026-08-03: patched: Commit e34f4ba349d55cd1849f0bcf4cf46552732e2db7