# CVE-2025-12343: Ffmpeg: double-free vulnerability in ffmpeg tensorflow dnn backend

> A double-free flaw in FFmpeg's TensorFlow backend allows attackers to cause a denial of service via crafted DNN models.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **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:** Yes
- **Published:** 18 Feb 2026
- **Updated:** 25 Feb 2026
- **Also known as:** DEBIAN-CVE-2025-12343, GHSA-2g52-f4rf-8vm9, JLSEC-2026-642, MINI-6p56-2x6q-73q9, UBUNTU-CVE-2025-12343

## What is CVE-2025-12343?

CVE-2025-12343 is a low-severity use after free vulnerability in Ffmpeg Ffmpeg, published on 18 Feb 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 flaw was found in FFmpeg’s TensorFlow backend within the libavfilter/dnn_backend_tf.c source file. The issue occurs in the dnn_execute_model_tf() function, where a task object is freed multiple times in certain error-handling paths. This redundant memory deallocation can lead to a double-free condition, potentially causing FFmpeg or any application using it to crash when processing TensorFlow-based DNN models. This results in a denial-of-service scenario but does not allow arbitrary code execution under normal conditions.

Weakness: CWE-415 (Double Free)

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

It affects 1 product.


Products: Ffmpeg Ffmpeg.

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

Apply the vendor's patch.

## Is CVE-2025-12343 being exploited?

There is no known exploitation of CVE-2025-12343 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-12343 and fix it if it is affected.

What it is: CVE-2025-12343 is a low-severity use after free vulnerability in Ffmpeg Ffmpeg, published on 18 Feb 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: There is no known exploitation of CVE-2025-12343 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-12343/ (Markdown: https://insights.sbomify.com/CVE-2025-12343/index.md)
```

## Sources

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

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