# CVE-2026-14790: GPAC Media File write_nhml.c nhmldump_send_frame null pointer dereference

> A local attacker can cause a denial of service in GPAC via a null pointer dereference in the media file handler.

- **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:** 6 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-14790, GHSA-2287-vqgx-x5qm, UBUNTU-CVE-2026-14790

## What is CVE-2026-14790?

CVE-2026-14790 is a medium-severity vulnerability in GPAC, published on 6 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw has been found in GPAC 26.02.0. This affects the function nhmldump_send_frame of the file src/filters/write_nhml.c of the component Media File Handler. Executing a manipulation can lead to null pointer dereference. The attack requires local access. The exploit has been published and may be used. This patch is called bd1d94e70e3bef364c07c5a1d94eca5c9f56e160. A patch should be applied to remediate this issue. The project explains: "I would consider most of these more as bugs than vulns but anyway they're good to fix".

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2026-14790 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14790 is a medium-severity vulnerability in GPAC, published on 6 Jul 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-14790 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-14790/ (Markdown: https://insights.sbomify.com/CVE-2026-14790/index.md)
```

## Sources

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

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