# CVE-2025-1594: FFmpeg AAC Encoder aacenc_tns.c ff_aac_search_for_tns stack-based overflow

> A stack-based buffer overflow in FFmpeg's AAC encoder allows remote attackers to execute arbitrary code or cause denial of service.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **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:** Yes
- **Published:** 23 Feb 2025
- **Updated:** 24 Feb 2025
- **Also known as:** DEBIAN-CVE-2025-1594, GHSA-37pp-xmcw-vg4w, JLSEC-2025-151, UBUNTU-CVE-2025-1594, USN-7738-1

## What is CVE-2025-1594?

CVE-2025-1594 is a medium-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 23 Feb 2025. 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 vulnerability, which was classified as critical, was found in FFmpeg up to 7.1. This affects the function ff_aac_search_for_tns of the file libavcodec/aacenc_tns.c of the component AAC Encoder. The manipulation leads to stack-based buffer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Ffmpeg Ffmpeg.

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

Upgrade to a fixed version.

## Is CVE-2025-1594 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1594 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-1594 and fix it if it is affected.

What it is: CVE-2025-1594 is a medium-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 23 Feb 2025. 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-1594 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-1594/ (Markdown: https://insights.sbomify.com/CVE-2025-1594/index.md)
```

## Sources

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

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