# CVE-2025-60482: Use after free in n/a

> Attackers can cause a denial of service in GPAC MP4Box by tricking users into opening a crafted AC4 file, leading to a heap use-after-free.

- **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:** 19 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-6v2v-xgp8-x2q9, UBUNTU-CVE-2025-60482

## What is CVE-2025-60482?

CVE-2025-60482 is a medium-severity use after free vulnerability in n/a, published on 19 Oct 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 heap use-after-free in the gf_odf_ac4_cfg_clean_list function (/odf/descriptors.c) of GPAC Project/MP4Box 2.5-DEV-rev1593-gfe88c3545-master allows attackers to cause a Denial of Service (DoS) via supplying a crafted AC4 file.

Weakness: CWE-416 (Use After Free)

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


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

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

## Is CVE-2025-60482 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60482 is a medium-severity use after free vulnerability in n/a, published on 19 Oct 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-2025-60482 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-2025-60482/ (Markdown: https://insights.sbomify.com/CVE-2025-60482/index.md)
```

## Sources

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

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