dbcve.org
FfmpegApplication

CVE-2026-64831

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 8.0 through 8.1.2 contains a stack buffer overflow vulnerability in the Vulkan HEVC hardware decoder that allows remote attackers to overwrite return addresses and adjacent stack frames by supplying a crafted HEVC/H.265 bitstream. Attackers can embed a malicious vps_num_hrd_parameters value exceeding HEVC_MAX_SUB_LAYERS in any supported container format to overflow stack-allocated arrays in the vk_hevc_end_frame function, potentially achieving arbitrary code execution.

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

Stack buffer overflow in FFmpeg's Vulkan HEVC hardware decoder where a crafted HEVC/H.265 bitstream with vps_num_hrd_parameters exceeding HEVC_MAX_SUB_LAYERS overflows stack-allocated arrays in the vk_hevc_end_frame function, allowing attackers to overwrite return addresses and adjacent stack frames for potential arbitrary code execution.

MitigationUpgrade FFmpeg to version 8.1.3 or later. Until patched, avoid processing untrusted HEVC streams through the Vulkan hardware decoder or disable Vulkan hardware acceleration entirely.

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:>= 8.0, <= 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. Verify FFmpeg version is within affected range
    Run 'ffmpeg -version' and check the version number. Affected versions are >= 8.0 and <= 8.1.2.
    Affected if Version shows 8.0, 8.1, 8.1.1, or 8.1.2
  2. Confirm Vulkan support is compiled into FFmpeg
    Run 'ffmpeg -hide_banner -hwaccels' and look for 'vulkan' in the list of available hardware accelerators.
    Affected if vulkan appears in the hwaccel list, indicating Vulkan support is enabled in this build
  3. Check if Vulkan HEVC decoding is available
    Run 'ffmpeg -hide_banner -decoders' | grep -i hevc and look for entries with 'hevc_vulkan' or similar Vulkan-based HEVC decoder.
    Affected if A Vulkan-based HEVC hardware decoder (hevc_vulkan) is listed as available
  4. Identify if HEVC content is being decoded via Vulkan
    Inspect any active FFmpeg processes or transcoding pipelines. Use 'ps aux | grep ffmpeg' and review command lines for '-hwaccel vulkan' or '-c:v hevc_vulkan' flags.
    Affected if FFmpeg is actively processing HEVC/H.265 streams using Vulkan hardware acceleration (hwaccel vulkan or hevc_vulkan decoder)

Your environment is affected if you have FFmpeg versions 8.0 through 8.1.2 with Vulkan support enabled AND you process HEVC/H.265 content using Vulkan hardware decoding.

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

Upgrade FFmpeg to version 8.1.3 or later. Until patched, avoid processing untrusted HEVC streams through the Vulkan hardware decoder or disable Vulkan hardware acceleration entirely.

Recommended fix Moderate confidence

FFmpeg 8.1.3 or latest stable 8.x release (check ffmpeg.org for current stable release)

  1. 1. Identify the current FFmpeg version by running 'ffmpeg -version' to confirm if versions 8.0 through 8.1.2 are in use
  2. 2. Download or obtain the latest stable FFmpeg release from the official website (ffmpeg.org) or trusted package repositories
  3. 3. For Linux distributions: use package manager updates (e.g., 'sudo apt update && sudo apt upgrade ffmpeg' for Debian/Ubuntu, or 'sudo dnf update ffmpeg' for Fedora/RHEL)
  4. 4. For Windows/macOS: download pre-built binaries from ffmpeg.org or use package managers like Chocolatey ('choco install ffmpeg') or Homebrew ('brew install ffmpeg')
  5. 5. Verify the new version after installation with 'ffmpeg -version'
  6. 6. Test that critical HEVC/Vulkan decoding functionality works as expected with the new build
Caveat Minimal risk - routine security update; verify any custom HEVC/Vulkan workflows after upgrade

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

Fix this in Ffmpeg Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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