dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2026-8461

HIGH · 8.8 CVSS v3.1 Published 2026-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
An out-of-bounds write vulnerability in FFmpeg's libavcodec library, specifically in the MagicYUV decoder, allows denial-of-service and, in some cases, can be exploited for remote code execution. This vulnerability is associated with the file libavcodec/magicyuv.C. This issue affects FFmpeg before version 8.1.2.

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

An out-of-bounds write vulnerability exists in FFmpeg's libavcodec library within the MagicYUV decoder (magicyuv.c). The vulnerability allows an attacker to trigger memory corruption via specially crafted MagicYUV video files, potentially leading to denial of service or remote code execution. This issue affects all FFmpeg versions prior to 8.1.2.

MitigationUpgrade FFmpeg to version 8.1.2 or later to patch the vulnerability in the MagicYUV decoder. If immediate upgrading is not feasible, disable MagicYUV codec support in FFmpeg builds or implement input validation/filtering for MagicYUV files at the application layer.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 examine the version number in the output
    Affected if Version is earlier than 8.1.2 (e.g., 8.1.1, 7.x, 6.x, etc.)
  2. Verify MagicYUV decoder availability
    Run 'ffmpeg -hide_banner -decoders 2>&1 | grep -i magicyuv'
    Affected if The MagicYUV decoder appears in the list of available decoders
  3. Confirm MagicYUV encoder support
    Run 'ffmpeg -hide_banner -encoders 2>&1 | grep -i magicyuv'
    Affected if The MagicYUV encoder appears in the list of available encoders (indicates compile-time support)
  4. Check libavcodec library version
    Run 'ffmpeg -version 2>&1 | grep libavcodec' to identify the library version bundled with FFmpeg
    Affected if libavcodec version is earlier than 8.1.2

A system is affected if FFmpeg (or libavcodec) version is below 8.1.2 AND the MagicYUV decoder or encoder is compiled into the binary (magicYUV support is present).

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade FFmpeg to version 8.1.2 or later to patch the vulnerability in the MagicYUV decoder. If immediate upgrading is not feasible, disable MagicYUV codec support in FFmpeg builds or implement input validation/filtering for MagicYUV files at the application layer.

Recommended fix High confidence

FFmpeg 8.1.2 or later

  1. Identify the current FFmpeg version installed by running `ffmpeg -version`
  2. Download FFmpeg version 8.1.2 or later from the official website (https://ffmpeg.org/download.html) or your distribution's package repository
  3. For source compilation: Clone the FFmpeg repository and checkout version 8.1.2 or later tags using `git checkout n8.1.2` or higher
  4. Compile and install the new version following standard build instructions
  5. Alternatively, update via package manager: on Debian/Ubuntu run `sudo apt update && sudo apt install ffmpeg`, on RHEL/CentOS run `sudo dnf update ffmpeg`
  6. Verify the installation succeeded by running `ffmpeg -version` to confirm version 8.1.2 or later is installed
  7. Test that dependent applications continue to function correctly with the updated FFmpeg library
Caveat Security patch releases typically have minimal breaking changes, but test critical workflows before deploying to production as minor behavioral changes in codec handling may occur

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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