# OSV-2026-767: Heap-use-after-free in gf_sg_reset

> A heap-use-after-free vulnerability in the scene graph reset function allows attackers to cause crashes or potentially execute code via crafted media files.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2026

## What is OSV-2026-767?

OSV-2026-767 is an use after free vulnerability in gpac, published on 18 May 2026. 

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=513912488

```
Crash type: Heap-use-after-free READ 8
Crash state:
gf_sg_reset
gf_sg_del
fuzz_scene.c
```

## Which versions are affected by OSV-2026-767?

1 open source package ship an affected version, including gpac.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gpac` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2026-767?

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

## Is OSV-2026-767 being exploited?

There is no known exploitation of OSV-2026-767 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2026-767 and fix it if it is affected.

What it is: OSV-2026-767 is an use after free vulnerability in gpac, published on 18 May 2026. 
Exploitation: There is no known exploitation of OSV-2026-767 in the wild and no public exploit code.

Affected packages and fixed versions:
- gpac (OSS-Fuzz): affected all versions; no fix listed

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/OSV-2026-767/ (Markdown: https://insights.sbomify.com/OSV-2026-767/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2026-767

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