# CVE-2026-88339: Null dereference in n/a

> An attacker can cause a denial of service in GPAC by providing a crafted file that triggers a NULL pointer dereference during field cloning.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-gphj-3jjc-cfmg, UBUNTU-CVE-2026-88339

## What is CVE-2026-88339?

CVE-2026-88339 is a medium-severity vulnerability in n/a, published on 22 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A NULL pointer dereference vulnerability exists in the gf_sg_vrml_field_clone() function of GPAC 2d7da22e (26.08-DEV). The vulnerability occurs when cloning a PROTO default SFImage field with a NULL source pointer. An attacker can provide a specially crafted input file that triggers the condition, resulting in application crash and denial of service.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

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

## Is CVE-2026-88339 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88339 is a medium-severity vulnerability in n/a, published on 22 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88339 exists.

Affected product: n/a. 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-88339/ (Markdown: https://insights.sbomify.com/CVE-2026-88339/index.md)
```

## Sources

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

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