# CVE-2026-71614: Code injection in n/a

> An attacker can execute arbitrary code in GPAC via crafted media files, requiring users to apply the latest security patch.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-c2fm-vm9m-g9xv, UBUNTU-CVE-2026-71614

## What is CVE-2026-71614?

CVE-2026-71614 is a high-severity code injection vulnerability in n/a, published on 9 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in GPAC c2dee3aff638cd96f9617ac5b17dc2868cd90ef3 allows an attacker to execute arbitrary code via the src/media_tools/dvb_mpe.c, descriptorTime_slice_fec_identifier() and gf_m2ts_ipdatagram_reader() components. Fixed in 0e4093392e1f847c90d20e031e893cd942fef938.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-71614 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71614 is a high-severity code injection vulnerability in n/a, published on 9 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-71614 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-71614/ (Markdown: https://insights.sbomify.com/CVE-2026-71614/index.md)
```

## Sources

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

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