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.
CVE-2025-12343
MEDIUMNVD 5.55.5Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory enrichment pending alignment with NVD CVSS.
Triggered by: NVD CVSS baseline
Sources: ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(low)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity55% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 5%
- KEV
- Not listed
Published
February 18, 2026
Last Modified
June 17, 2026
References (2)
- patrick@puiterwijkhttps://access.redhat.com/security/cve/CVE-2025-12343
- patrick@puiterwijkhttps://bugzilla.redhat.com/show_bug.cgi?id=2406533
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 14:12 UTCEPSS rescore
- 2026-07-27 13:27 UTCEG score recompute
- 2026-07-27 13:27 UTCGHSA enrichment
Related CVEs(same CWE)
Same CWE
10 shownCWE-415
- CVE-2007-4773EG 9.8CRITICAL
- CVE-2016-8619NVD 5.3EG 9.8EPSS p91CRITICAL
- CVE-2016-8618NVD 5.3EG 9.8EPSS p91CRITICAL
- CVE-2015-9165EG 9.8CRITICAL
- CVE-2017-18201EG 9.8CRITICAL
- CVE-2017-18174EG 9.8CRITICAL
- CVE-2017-1000232EG 9.8CRITICAL
- CVE-2017-1000231EG 9.8CRITICAL
- CVE-2017-16820EG 9.8CRITICAL
- CVE-2017-14952EG 9.8EPSS p91CRITICAL
Frequently asked(5)
What is CVE-2025-12343?
CVE-2025-12343 is a medium vulnerability published on February 18, 2026. A flaw was found in FFmpeg’s TensorFlow backend within the libavfilter/dnnbackendtf.c source file. The issue occurs in the dnnexecutemodel_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…
When was CVE-2025-12343 disclosed?
CVE-2025-12343 was first published in the National Vulnerability Database on February 18, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-12343 actively exploited?
CVE-2025-12343 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.4% of all scored CVEs.
What is the CVSS score of CVE-2025-12343?
CVE-2025-12343 has a CVSS v3 base score of 5.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2025-12343?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-12343, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-12343
Is Your Infrastructure Affected by CVE-2025-12343?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.