VulnerabilityPublished 18 Feb 2026Updated 25 Feb 2026

CVE-2025-12343: ffmpeg · Double Free

Affects ffmpegSource CVE Database V5

Not known to be exploited · CVSS 3.3 Low : upgrade to 8.1 when convenient.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score

3.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.1

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade ffmpeg to 8.1.

Affected software

Product	Affected	Fixed in
GitHubffmpeg`pkg:github/ffmpeg`Other threats	Affected >=6.1 <8.1	Fixed in 8.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-12343, organizations should upgrade FFmpeg to a version where this double-free flaw is patched once available. If you cannot patch yet, consider disabling or avoiding the use of the TensorFlow backend filter (libavfilter/dnn_backend_tf.c) in FFmpeg, especially in environments processing untrusted or user-supplied TensorFlow DNN models. Implement strict access controls to limit local user permissions and reduce the risk of exploitation via user interaction. Employ application whitelisting and monitoring to detect abnormal FFmpeg crashes or unusual TensorFlow model processing activity. In containerized or virtualized environments, isolate FFmpeg processes to minimize impact scope. Regularly audit and update all dependencies related to FFmpeg and TensorFlow integration. Finally, maintain robust incident response procedures to quickly recover from any denial-of-service events caused by this vulnerability.

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.

Impact

The primary impact of CVE-2025-12343 is denial-of-service due to application crashes triggered by the double-free condition. Organizations using FFmpeg 6.1 for TensorFlow-based DNN processing may experience unexpected service interruptions, degraded availability, or system instability. This can affect media streaming services, video processing pipelines, AI inference workloads, and any software embedding FFmpeg for neural network filtering. Although the vulnerability does not allow code execution or data compromise, the resulting crashes could disrupt critical workflows, cause downtime, and require manual intervention to restart services. In environments with high availability requirements or automated processing, such disruptions could lead to operational delays and increased support costs. Since exploitation requires local access and user interaction, remote exploitation risk is minimal, reducing the threat to internet-facing systems. However, insider threats or compromised user accounts could trigger the vulnerability. No known exploits in the wild further reduce immediate risk, but organizations should remain vigilant.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 07:48 UTC

Technical details

References

Community reviews

Related threats