# CVE-2025-70299: Memory corruption in n/a

> Attackers can cause a denial of service via a crafted AVI file due to a heap overflow in the GPAC multimedia library.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jan 2026
- **Updated:** 15 Jan 2026
- **Also known as:** DEBIAN-CVE-2025-70299, GHSA-rcx9-rrrc-j64v, UBUNTU-CVE-2025-70299

## What is CVE-2025-70299?

CVE-2025-70299 is a medium-severity memory corruption vulnerability in Gpac Gpac, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A heap overflow in the avi_parse_input_file() function of GPAC v2.4.0 allows attackers to cause a Denial of Service (DoS) via a crafted AVI file.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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

It affects 1 product.


Products: Gpac Gpac.

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

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

## Is CVE-2025-70299 being exploited?

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

## Other vulnerabilities in Gpac Gpac

- [CVE-2023-46427](https://insights.sbomify.com/CVE-2023-46427/): Null dereference in n/a (critical 9.8)
- [CVE-2023-46932](https://insights.sbomify.com/CVE-2023-46932/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-36190](https://insights.sbomify.com/CVE-2022-36190/): Use after free in n/a (critical 9.8)
- [CVE-2021-28300](https://insights.sbomify.com/CVE-2021-28300/): Null dereference in n/a (critical 9.8)
- [CVE-2020-11558](https://insights.sbomify.com/CVE-2020-11558/): Use after free in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-70299 is a medium-severity memory corruption vulnerability in Gpac Gpac, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, 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-70299 exists.

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

## Sources

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

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