Quick answers
- Is CVE-2026-91091 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-91091 being exploited in the wild.
- How severe is CVE-2026-91091?
- Medium severity, with a CVSS score of 4.3, published 15 September 2026.
- Which products and versions are affected?
- Gpac up to f1219cde.
- Is there a fix for CVE-2026-91091?
- A patch was published on 2026-07-28: Patch commit 49dee5cad329cfed310c1682703df7daa47df31a merged Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-91091 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-91091?
- 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
The vulnerability exists in the gf_node_list_insert_child function within scenegraph/base_scenegraph.c, which handles node insertion in GPAC's scene graph component. The flaw leads to memory corruption that can be triggered by remote attackers without requiring authentication. The vulnerability is remotely exploitable and a public exploit is available. The issue has been patched in version abi-16.23 with commit 49dee5cad329cfed310c1682703df7daa47df31a.
Affected products
- GPAC GPAC up to f1219cde
Timeline
- 2026-07-28: patched: Patch commit 49dee5cad329cfed310c1682703df7daa47df31a merged
- 2026-09-15: disclosed