dbcve.org
FfmpegApplication

CVE-2026-64832

HIGH · 8.8 CVSS v3.1 Published 2026-07-22
Fix available
A fix is available. Upgrade to after 8.1.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 4 weeks old

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

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 in FFmpeg's NVIDIA NVDEC hardware decoder (libavcodec/nvdec.c) allows memory corruption via crafted video files. When decoder surfaces are exhausted, 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 decoder context in any FFmpeg-based application using NVDEC hardware-accelerated decoding.

MitigationUpdate FFmpeg to version 8.1.3 or later which contains the fix for this double-free vulnerability, or disable NVDEC hardware acceleration in affected applications until patching is feasible.

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:>= 4.4, <= 8.1.2

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 locate the version number in the output (e.g., 4.4, 5.0, 6.0, 7.0, 8.0, 8.1.2)
    Affected if Version is >= 4.4 and <= 8.1.2
  2. Verify NVDEC hardware decoder support is compiled in
    Run 'ffmpeg -hide_banner -hwaccels' and look for 'nvdec' in the list of available hardware accelerations
    Affected if nvdec appears in the hardware acceleration list and version is in the affected range
  3. Confirm NVDEC is actively in use for decoding
    Inspect the ffmpeg command line or application configuration for '-hwaccel nvdec', '-c:v h264_nvdec', '-c:v hevc_nvdec', or similar NVDEC codec flags; or examine runtime logs for 'Using NVACCEL' messages with NVDEC
    Affected if NVDEC hardware acceleration is enabled and being used for decoding with an affected FFmpeg version

User is affected if FFmpeg version is between 4.4 and 8.1.2 inclusive AND NVDEC hardware-accelerated decoding is actively being used, since the double-free only triggers during NVDEC decode operations when decoder surfaces are exhausted.

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 a release after 8.1.2
Interim mitigation

Update FFmpeg to version 8.1.3 or later which contains the fix for this double-free vulnerability, or disable NVDEC hardware acceleration in affected applications until patching is feasible.

Recommended fix Moderate confidence

FFmpeg 8.1.3 or later (latest stable release)

  1. 1. Identify the current FFmpeg version in use by running 'ffmpeg -version'
  2. 2. Check if the version is between 4.4 and 8.1.2 inclusive, as these versions contain the double-free vulnerability in NVDEC
  3. 3. If using an affected version, upgrade to the latest stable FFmpeg release (version 8.1.3 or later)
  4. 4. Verify the upgrade was successful by running 'ffmpeg -version' and confirming the new version number
  5. 5. Test NVDEC hardware-accelerated decoding with the upgraded FFmpeg to confirm functionality
Caveat Minor - upgrading FFmpeg may introduce changes in codec support or API behavior; test critical video processing pipelines after upgrade

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

Fix this in Ffmpeg Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-64832 — 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-2026-64832 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