Quick answers
- Is CVE-2026-92473 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92473 being exploited in the wild.
- How severe is CVE-2026-92473?
- Low severity, with a CVSS score of 3.3, published 16 September 2026.
- Which products and versions are affected?
- GPAC Project GPAC 26.08-DEV.
- Is there a fix for CVE-2026-92473?
- A patch was published on 2026-08-03: Fix available in abi-16.24 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92473 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-92473?
- Check whether anything you run is named in the advisory. 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_sg_command_del function of src/scenegraph/commands.c within the BIFS Handler component of GPAC 26.08-DEV. The vulnerability is triggered through local manipulation of the scenegraph command processing logic. The attack vector is local and does not require special privileges or network access. An attacker can exploit this by providing a malicious input file to trigger memory access violations. A patch is available in version abi-16.24 (commit e34f4ba349d55cd1849f0bcf4cf46552732e2db7).
Affected products
- GPAC Project GPAC 26.08-DEV
Timeline
- 2026-09-16: disclosed
- 2026-08-03: patched: Fix available in abi-16.24