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

> A memory leak in FFmpeg's IAMF component allows attackers to cause denial of service through resource exhaustion.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Feb 2025
- **Updated:** 19 Feb 2025
- **Also known as:** GHSA-cgf4-78xq-c6wj, MINI-p86p-xcgf-5jp9, UBUNTU-CVE-2025-25469

## What is CVE-2025-25469?

CVE-2025-25469 is a medium-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 18 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FFmpeg git-master before commit d5873b was discovered to contain a memory leak in the component libavutil/iamf.c.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

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

It affects 1 product.


Products: Ffmpeg Ffmpeg.

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

Apply the vendor's patch.

## Is CVE-2025-25469 being exploited?

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

## Other vulnerabilities in Ffmpeg Ffmpeg

- [CVE-2013-0864](https://insights.sbomify.com/CVE-2013-0864/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-0872](https://insights.sbomify.com/CVE-2013-0872/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-0873](https://insights.sbomify.com/CVE-2013-0873/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-4265](https://insights.sbomify.com/CVE-2013-4265/): Null dereference in n/a (critical 10.0)
- [CVE-2011-3937](https://insights.sbomify.com/CVE-2011-3937/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25469 is a medium-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 18 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25469 exists.

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

## Sources

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

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