FFmpeg versions 4.4 through 8.1.2 contain a double-free vulnerability in the NVIDIA NVDEC hardware decoder within libavcodec/nvdec.c that allows attackers to trigger memory corruption by supplying a crafted video file. When no decoder surfaces remain, the ff_nvdec_start_frame_sep_ref error path frees memory via nvdec_fdd_priv_free while the calling layer subsequently frees the same frame description data, resulting in a double-free of the underlying decoder context in any FFmpeg-based application using NVDEC hardware-accelerated decoding.
CVE-2026-64832
HIGHPre-NVD 8.88.8—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-22. a secondary CVSS source baseline 8.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EG Risk
- 40(Track)EG Risk 40/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 computedSeverity88% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 27.2%
- KEV
- Not listed
Published
July 22, 2026
Last Modified
July 22, 2026
Advisory Details (3)
Auto-updated Jul 22, 2026No patch confirmed yet.
generic
FFmpeg 4.4 - 8.1.2 Double-Free in NVDEC Hardware Decoder via nvdec.c | Advisories | VulnCheck
https://www.vulncheck.com/advisories/ffmpeg-double-free-in-nvdec-hardware-decoder-via-nvdec-cgeneric
#23664 - avcodec/nvdec: don't double free the fdd-owned context on the sep_ref error path - FFmpeg/FFmpeg - FFmpeg Forgejo
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/23664generic
avcodec/nvdec: don't double free the fdd-owned context on the sep_ref error path · 4c6217477f - FFmpeg/FFmpeg - FFmpeg Forgejo
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/4c6217477fc64305055b37d9d1d0d76d30e37f97Vendor Advisories for CVE-2026-64832(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× 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-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 21:10 UTCEG score recompute
- 2026-07-22 21:09 UTCGHSA enrichment
- 2026-07-22 18:40 UTCEG score recompute
- 2026-07-22 18:39 UTCGHSA enrichment
- 2026-07-22 17:36 UTCEG score recompute
- 2026-07-22 17:35 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-415
- CVE-2018-0101EG 10.0EPSS 100%CRITICAL
- CVE-2007-4773EG 9.8CRITICAL
- CVE-2018-20996EG 9.8CRITICAL
- CVE-2018-20991EG 9.8CRITICAL
- CVE-2018-20961EG 9.8EPSS 93%CRITICAL
- CVE-2018-3985EG 9.8CRITICAL
- CVE-2018-18751EG 9.8EPSS 90%CRITICAL
- CVE-2018-17825EG 9.8CRITICAL
- CVE-2018-16402EG 9.8CRITICAL
- CVE-2016-8619NVD 5.3EG 9.8EPSS 91%MEDIUM
Frequently asked(5)
What is CVE-2026-64832?
CVE-2026-64832 is a high vulnerability published on July 22, 2026. FFmpeg versions 4.4 through 8.1.2 contain a double-free vulnerability in the NVIDIA NVDEC hardware decoder within libavcodec/nvdec.c that allows attackers to trigger memory corruption by supplying a crafted video file. When no decoder surfaces remain, the ffnvdecstartframesepref error path frees…
When was CVE-2026-64832 disclosed?
CVE-2026-64832 was first published in the National Vulnerability Database on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64832 actively exploited?
CVE-2026-64832 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-64832?
CVE-2026-64832 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-64832?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64832, 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-2026-64832
Is Your Infrastructure Affected by CVE-2026-64832?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.