NEWS

FFmpeg Fixes PixelSmash Flaw in Widely Used Video Decoder

FFmpeg has patched a critical vulnerability dubbed PixelSmash that could enable remote code execution on Jellyfin servers and denial-of-service conditions...

Dylan H.

News Desk

June 22, 2026
3 min read
FFmpeg Fixes PixelSmash Flaw in Widely Used Video Decoder

The FFmpeg project has released a patch addressing a newly disclosed vulnerability nicknamed PixelSmash (tracked as CVE-2025-32956), a flaw in the widely used open-source video decoder that carries serious consequences for a broad ecosystem of downstream applications.

PixelSmash can be exploited to achieve remote code execution (RCE) under specific conditions — most notably on Jellyfin media servers — and can trigger denial-of-service (DoS) conditions in a wide range of other software including:

  • Kodi (media center)
  • Emby (media server)
  • Nextcloud (via media processing plugins)
  • PhotoPrism (photo management)
  • OBS Studio (streaming software)

Technical Overview

The vulnerability exists in FFmpeg's video decoding pipeline and is triggered during the processing of maliciously crafted video files. A remote attacker who can cause a vulnerable application to process attacker-controlled media — for example, via a shared link, an upload feature, or an external media source — may be able to:

  1. Cause a heap corruption during pixel data processing
  2. Under specific memory layout conditions, achieve arbitrary code execution
  3. At minimum, reliably crash the host process (DoS)

The "PixelSmash" name reflects the nature of the bug: malformed pixel buffer handling that can smash heap metadata or stack boundaries in vulnerable decoders.

Affected Software and Versions

ApplicationImpactNotes
JellyfinRCE (High)Transcoding path most exposed
KodiDoS (Medium)Crash on malformed file
EmbyDoS (Medium)Media ingest pipeline
NextcloudDoS (Medium)Depends on media app install
PhotoPrismDoS (Medium)Video thumbnail generation
OBS StudioDoS (Medium)Source media processing

Remediation Steps

Update FFmpeg immediately to the patched version. Downstream application maintainers have been notified and patches for Jellyfin, Kodi, and other affected projects are expected to follow rapidly.

If you cannot patch immediately:

  • Disable external/untrusted media sources in affected applications
  • Restrict file upload features to trusted users only
  • Isolate transcoding services (e.g. run Jellyfin in a container with limited privileges)
  • Monitor for crash loops in media-processing applications as a potential indicator of exploitation

Why This Matters

FFmpeg is one of the most widely deployed open-source libraries on the planet. It underpins media processing in web browsers, streaming platforms, operating systems, and thousands of applications. A critical flaw in FFmpeg is effectively a flaw in the entire media-processing ecosystem.

Self-hosted media server operators running Jellyfin, Emby, or Kodi with internet-accessible interfaces should treat this as a priority patch.


Source: BleepingComputer