# CVE-2026-92473: GPAC BIFS commands.c gf_sg_command_del use after free

> A local attacker can trigger a use-after-free in GPAC's BIFS handler, potentially leading to code execution or denial of service.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-wf7c-2jr3-g777, UBUNTU-CVE-2026-92473

## What is CVE-2026-92473?

CVE-2026-92473 is a medium-severity use after free vulnerability in GPAC, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was identified in GPAC 26.08-DEV. The impacted element is the function gf_sg_command_del of the file src/scenegraph/commands.c of the component BIFS Handler. The manipulation leads to use after free. The attack needs to be performed locally. The exploit is publicly available and might be used. Upgrading to version abi-16.24 is sufficient to resolve this issue. The identifier of the patch is e34f4ba349d55cd1849f0bcf4cf46552732e2db7. It is suggested to upgrade the affected component.

Weakness: CWE-416 (Use After Free), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-92473?


## How do I fix CVE-2026-92473?

No fix has been published for CVE-2026-92473 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92473 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92473 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92473 and fix it if it is affected.

What it is: CVE-2026-92473 is a medium-severity use after free vulnerability in GPAC, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92473 exists.

Affected product: GPAC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92473/ (Markdown: https://insights.sbomify.com/CVE-2026-92473/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92473
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92473
- OSV: https://osv.dev/vulnerability/CVE-2026-92473

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92473/
Summaries are generated and may contain mistakes; the official description above is the record.