OSV-2026-798 Heap-use-after-free in ReplaceDEFNode
Not scored
Published
Check this codebase for OSV-2026-798 and fix it if it is affected.
What it is: OSV-2026-798 is an use after free vulnerability in gpac, published on 22 May 2026.
Exploitation: There is no known exploitation of OSV-2026-798 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-798/ (Markdown: https://insights.sbomify.com/OSV-2026-798/index.md)
A heap-use-after-free vulnerability in libgpac allows attackers to potentially execute arbitrary code or cause a denial of service via crafted media files.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2026-798?
OSV-2026-798 is an use after free vulnerability in gpac, published on 22 May 2026.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=515134929
Crash type: Heap-use-after-free READ 8
Crash state:
ReplaceDEFNode
gf_sg_reset
gf_sg_del
Which versions are affected by OSV-2026-798?
1 open source package ship an affected version, including gpac.
| Package | Affected | Fixed in |
|---|---|---|
gpac OSS-Fuzz | All versions | None |
How do I fix OSV-2026-798?
No fix has been published for OSV-2026-798 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is OSV-2026-798 being exploited?
There is no known exploitation of OSV-2026-798 in the wild and no public exploit code.