# CVE-2026-71616: Denial of service in n/a

> An attacker can cause a denial of service in the GPAC multimedia library via the gf_route_media_complete_object function.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-95rr-7f3w-mphr, UBUNTU-CVE-2026-71616

## What is CVE-2026-71616?

CVE-2026-71616 is a medium-severity denial of service 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 cause a denial of service via the function gf_route_media_complete_object(). Fixed in 3c4e6c5b3e0c6fa9b16d55599701a08354538fab.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2026-71616 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71616 is a medium-severity denial of service 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-71616 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-71616/ (Markdown: https://insights.sbomify.com/CVE-2026-71616/index.md)
```

## Sources

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

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