Quick answers
- Is CVE-2026-90825 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-90825 being exploited in the wild.
- How severe is CVE-2026-90825?
- Low severity, with a CVSS score of 3.3, published 14 September 2026.
- Which products and versions are affected?
- Gpac 26.07.0.
- Is there a fix for CVE-2026-90825?
- A patch was published on 2026-07-27: Patch commit 9eb40df4448b88d6a6ce3454657c06f47eff0b24 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-90825 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-90825?
- 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_node_unregister function within scenegraph/base_scenegraph.c of GPAC's MP4Box component. The vulnerability is triggered through the manipulation of scene graph node objects, allowing access to memory that has been previously freed. Local access is required to exploit this vulnerability. An attacker with local access can craft malicious input to trigger the flaw, potentially leading to information disclosure, denial of service, or code execution. A patch is available in commit 9eb40df4448b88d6a6ce3454657c06f47eff0b24, and upgrading to version abi-16.23 or later addresses the issue.
Affected products
- GPAC GPAC 26.07.0
Timeline
- 2026-09-14: disclosed
- 2026-07-27: patched: Patch commit 9eb40df4448b88d6a6ce3454657c06f47eff0b24