# CVE-2025-71471: GPAC before 26.02.0 Uninitialized Memory Use in stbl_AddCTS()

> A crafted MP4 file can corrupt memory and crash GPAC when imported with MP4Box.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **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
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 16 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-87vf-j42j-9rc2, UBUNTU-CVE-2025-71471

## What is CVE-2025-71471?

CVE-2025-71471 is a medium-severity memory corruption vulnerability in gpac, published on 16 Nov 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

GPAC before 26.02.0 contains a use of uninitialized memory vulnerability in stbl_AddCTS() that allows attackers to corrupt sample table data via crafted MP4 files. Attackers can supply an MP4 with out-of-order composition time offsets for MP4Box import, triggering invalid memory access in gf_list_get() and crashing the process.

Weakness: CWE-908 (Use of Uninitialized Resource)

## Which versions are affected by CVE-2025-71471?

1 open source package ship an affected version, including gpac/gpac.

An affected version is exposed as installed. No special setting or call is needed.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `gpac/gpac` | GitHub | `pkg:github/gpac/gpac` | All versions | 26.02.0 |

## How do I fix CVE-2025-71471?

Upgrade gpac/gpac to 26.02.0 or later.

## Is CVE-2025-71471 being exploited?

There is no known exploitation of CVE-2025-71471 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-71471 and fix it if it is affected.

What it is: CVE-2025-71471 is a medium-severity memory corruption vulnerability in gpac, published on 16 Nov 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: There is no known exploitation of CVE-2025-71471 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected packages and fixed versions:
- gpac/gpac (GitHub): affected all versions; fixed in 26.02.0

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-2025-71471/ (Markdown: https://insights.sbomify.com/CVE-2025-71471/index.md)
```

## Sources

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

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