# CVE-2025-10256: Ffmpeg: null pointer dereference in firequalizer filter (libavfilter/af_firequalizer.c)

> An attacker can cause a denial of service by tricking a user into processing a crafted media file with the Firequalizer filter enabled in FFmpeg.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **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 2026
- **Updated:** 25 Feb 2026
- **Also known as:** DEBIAN-CVE-2025-10256, GHSA-c96q-rf2r-2xj8, JLSEC-2026-641, MINI-gxj3-3j58-w22x, SUSE-SU-2026:3149-1, UBUNTU-CVE-2025-10256

## What is CVE-2025-10256?

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

### Official description

A NULL pointer dereference vulnerability exists in FFmpeg’s Firequalizer filter (libavfilter/af_firequalizer.c) due to a missing check on the return value of av_malloc_array() in the config_input() function. An attacker could exploit this by tricking a victim into processing a crafted media file with the Firequalizer filter enabled, causing the application to dereference a NULL pointer and crash, leading to denial of service.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ffmpeg` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP7 | All versions | 3.4.2-150200.11.70.1 |
| `ffmpeg` | SUSE:Linux Enterprise Module for Package Hub 15 SP7 | All versions | 3.4.2-150200.11.70.1 |
| `ffmpeg` | SUSE:Linux Enterprise Workstation Extension 15 SP7 | All versions | 3.4.2-150200.11.70.1 |

Products: Ffmpeg Ffmpeg.

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

Apply the vendor's patch.

## Is CVE-2025-10256 being exploited?

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

## 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-10256 and fix it if it is affected.

What it is: CVE-2025-10256 is a medium-severity vulnerability in Ffmpeg Ffmpeg, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10256 in the wild and no public exploit code.

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

## Sources

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

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