dbcve.org
FfmpegApplication

CVE-2025-12343

MEDIUM · 5.5 CVSS v3.1 Published 2026-02-18
Fix available
A fix is available. Upgrade to 8.1 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A double-free vulnerability exists in FFmpeg's TensorFlow DNN backend (libavfilter/dnn_backend_tf.c) within the dnn_execute_model_tf() function. The issue occurs when error-handling paths incorrectly free a task object multiple times, leading to memory corruption and potential application crashes when processing TensorFlow-based deep neural network models.

MitigationUpdate to a patched version of FFmpeg that addresses the double-free in the TensorFlow backend error-handling paths. As a temporary measure, avoid processing untrusted TensorFlow DNN models until the update is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FfmpegApplication
Affected:>= 6.1, < 8.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed FFmpeg version
    Run 'ffmpeg -version' and look for the version number in the output (e.g., 6.1, 7.0, 8.0)
    Affected if The version is greater than or equal to 6.1 and less than 8.1
  2. Verify TensorFlow DNN backend support is built in
    Run 'ffmpeg -filters' and search for DNN-related filters, or run 'ffmpeg -version' and look for '--enable-libtensorflow' or similar TensorFlow flags in the configuration output
    Affected if TensorFlow backend support is present in the FFmpeg build
  3. Identify if DNN filtering is actively used
    Inspect any running FFmpeg commands or scripts that process media, looking for dnn_processing, dnn_detect, or similar DNN-based filters in the filter chain
    Affected if A DNN-based filter is being applied to media files or streams
  4. Confirm TensorFlow models are being processed
    Examine the command lines or configuration files using DNN filters, checking for .pb (protobuf) model files or references to TensorFlow-based model paths in the filter options
    Affected if TensorFlow (.pb) model files are being loaded by the DNN filter

You are affected if your FFmpeg version is between 6.1 and 8.1 (exclusive of 8.1) AND you are actively processing media using TensorFlow-based DNN models with the TensorFlow backend enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.1 or later
Fixed in 8.1
Interim mitigation

Update to a patched version of FFmpeg that addresses the double-free in the TensorFlow backend error-handling paths. As a temporary measure, avoid processing untrusted TensorFlow DNN models until the update is applied.

Recommended fix Moderate confidence

FFmpeg 8.1 or later

  1. Check current FFmpeg version using 'ffmpeg -version' to confirm the installation is within the affected range (6.1 to 8.0)
  2. Download FFmpeg version 8.1 or later from the official source (https://ffmpeg.org/download.html) or your distribution's package repository
  3. For package manager installations: update your package list and upgrade FFmpeg (e.g., 'apt update && apt upgrade ffmpeg' for Debian/Ubuntu, or 'yum update ffmpeg' for RHEL/CentOS)
  4. For source compilation: configure with './configure' and compile using 'make', then install with 'make install'
  5. Verify the new version is installed correctly by running 'ffmpeg -version'
  6. If using FFmpeg in an application, rebuild or restart the application to ensure it links against the updated library
Caveat Major version upgrades in FFmpeg may include API/ABI changes, codec support additions, or removed deprecated features; review the FFmpeg 8.0 release notes for any breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ffmpeg Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12343 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12343 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data