CVE-2026-64832

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM 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: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8(medium)
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 computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 28, 2026

Advisory Details (3)

Auto-updated Jul 22, 2026
No 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-c
generic

#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/23664
generic

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/4c6217477fc64305055b37d9d1d0d76d30e37f97

Vendor 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.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibswscale-ffmpeg3 (7:2.8.17-0ubuntu0.1+esm17) @ xenial2026-09-14ubuntu
ubuntulibswscale9 (7:8.0.1-3ubuntu2+esm4) @ resolute2026-09-14ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
ffmpeg7:4.3.2-0+deb11u2 ... 7:8.1.2-2 (91 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ffmpeg7:5.1.3-1 ... 7:9.0.1-1 (59 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ffmpeg7:7.1.1-1 ... 7:9.0.1-1 (23 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ffmpeg7:7.1.1-1 ... 7:8.0.1-3 (8 versions)7:8.1-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 26× in last 7d / 100× 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.

Showing the most recent 100 of 207 total refreshes for this CVE.

  1. 2026-09-14 16:48 UTCVendor advisory
  2. 2026-09-14 16:48 UTCGHSA enrichment
  3. 2026-09-14 02:41 UTCEG score recompute
  4. 2026-09-14 02:41 UTCVendor advisory
  5. 2026-09-14 02:41 UTCGHSA enrichment
  6. 2026-09-13 15:43 UTCVendor advisory
  7. 2026-09-13 15:43 UTCGHSA enrichment
  8. 2026-09-13 04:47 UTCVendor advisory
  9. 2026-09-13 04:47 UTCGHSA enrichment
  10. 2026-09-12 17:48 UTCEG score recompute
  11. 2026-09-12 17:48 UTCVendor advisory
  12. 2026-09-12 17:48 UTCGHSA enrichment
  13. 2026-09-12 06:38 UTCVendor advisory
  14. 2026-09-12 06:38 UTCGHSA enrichment
  15. 2026-09-11 19:33 UTCEG score recompute
  16. 2026-09-11 19:33 UTCVendor advisory
  17. 2026-09-11 19:33 UTCGHSA enrichment
  18. 2026-09-11 09:37 UTCEPSS rescore
  19. 2026-09-11 08:29 UTCVendor advisory
  20. 2026-09-11 08:29 UTCGHSA enrichment
  21. 2026-09-10 21:32 UTCEG score recompute
  22. 2026-09-10 21:32 UTCVendor advisory
  23. 2026-09-10 21:32 UTCGHSA enrichment
  24. 2026-09-09 09:14 UTCEG score recompute
  25. 2026-09-09 09:14 UTCVendor advisory
Show 75 more
  1. 2026-09-09 09:14 UTCGHSA enrichment
  2. 2026-09-08 22:01 UTCEPSS rescore
  3. 2026-09-07 21:41 UTCEG score recompute
  4. 2026-09-07 21:41 UTCVendor advisory
  5. 2026-09-07 21:41 UTCGHSA enrichment
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-06 08:42 UTCVendor advisory
  9. 2026-09-06 08:41 UTCGHSA enrichment
  10. 2026-09-05 19:34 UTCEG score recompute
  11. 2026-09-05 19:34 UTCVendor advisory
  12. 2026-09-05 19:34 UTCGHSA enrichment
  13. 2026-09-05 15:31 UTCEPSS rescore
  14. 2026-09-05 07:14 UTCEG score recompute
  15. 2026-09-05 07:14 UTCVendor advisory
  16. 2026-09-05 07:14 UTCGHSA enrichment
  17. 2026-09-04 13:53 UTCEG score recompute
  18. 2026-09-04 13:53 UTCGHSA enrichment
  19. 2026-09-04 05:07 UTCEPSS rescore
  20. 2026-09-02 14:12 UTCEPSS rescore
  21. 2026-09-01 23:40 UTCEG score recompute
  22. 2026-09-01 23:40 UTCGHSA enrichment
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-08-30 23:10 UTCEG score recompute
  26. 2026-08-30 23:10 UTCGHSA enrichment
  27. 2026-08-30 19:17 UTCEPSS rescore
  28. 2026-08-30 12:13 UTCEG score recompute
  29. 2026-08-30 12:13 UTCGHSA enrichment
  30. 2026-08-30 01:22 UTCEPSS rescore
  31. 2026-08-30 00:53 UTCEG score recompute
  32. 2026-08-30 00:53 UTCGHSA enrichment
  33. 2026-08-28 21:42 UTCEPSS rescore
  34. 2026-08-27 21:14 UTCEG score recompute
  35. 2026-08-27 21:14 UTCGHSA enrichment
  36. 2026-08-27 10:18 UTCGHSA enrichment
  37. 2026-08-26 19:58 UTCEG score recompute
  38. 2026-08-26 19:58 UTCGHSA enrichment
  39. 2026-08-26 14:47 UTCEPSS rescore
  40. 2026-08-26 06:54 UTCGHSA enrichment
  41. 2026-08-25 19:35 UTCEG score recompute
  42. 2026-08-25 19:35 UTCGHSA enrichment
  43. 2026-08-25 13:49 UTCEPSS rescore
  44. 2026-08-25 08:37 UTCGHSA enrichment
  45. 2026-08-24 21:41 UTCEG score recompute
  46. 2026-08-24 21:41 UTCGHSA enrichment
  47. 2026-08-24 10:16 UTCEG score recompute
  48. 2026-08-24 10:16 UTCGHSA enrichment
  49. 2026-08-23 23:19 UTCGHSA enrichment
  50. 2026-08-23 12:23 UTCGHSA enrichment
  51. 2026-08-23 01:26 UTCEG score recompute
  52. 2026-08-23 01:26 UTCGHSA enrichment
  53. 2026-08-23 00:19 UTCEPSS rescore
  54. 2026-08-22 14:28 UTCGHSA enrichment
  55. 2026-08-22 03:31 UTCEG score recompute
  56. 2026-08-22 03:31 UTCGHSA enrichment
  57. 2026-08-21 23:49 UTCEPSS rescore
  58. 2026-08-21 16:34 UTCGHSA enrichment
  59. 2026-08-21 05:35 UTCEG score recompute
  60. 2026-08-21 05:35 UTCGHSA enrichment
  61. 2026-08-20 22:55 UTCEPSS rescore
  62. 2026-08-20 18:38 UTCGHSA enrichment
  63. 2026-08-20 07:41 UTCGHSA enrichment
  64. 2026-08-19 20:44 UTCEG score recompute
  65. 2026-08-19 20:44 UTCGHSA enrichment
  66. 2026-08-19 17:04 UTCEPSS rescore
  67. 2026-08-19 06:30 UTCGHSA enrichment
  68. 2026-08-18 19:12 UTCEG score recompute
  69. 2026-08-18 19:12 UTCGHSA enrichment
  70. 2026-08-18 13:48 UTCEPSS rescore
  71. 2026-08-18 07:24 UTCGHSA enrichment
  72. 2026-08-17 20:28 UTCEG score recompute
  73. 2026-08-17 20:28 UTCGHSA enrichment
  74. 2026-08-17 13:47 UTCEPSS rescore
  75. 2026-08-17 08:16 UTCGHSA enrichment

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, with the most recent update on July 28, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 73.5% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64832

Explore →

Is Your Infrastructure Affected by CVE-2026-64832?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.