PixelSmash is a heap out-of-bounds write in FFmpeg's libavcodec MagicYUV decoder affecting versions before 8.1.2. The decoder and frame allocator calculate chroma-plane heights inconsistently for attacker-controlled odd slice-height values in sliced, subsampled MagicYUV video. Per-slice rounding can cumulatively cause the decoder to write an additional chroma row beyond the allocated heap buffer. The resulting corruption can crash the consuming process and may overwrite adjacent FFmpeg heap objects, including reference-counted buffer metadata.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
4 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This 16-file repository is an operational Linux proof-of-concept/lab for CVE-2026-8461, described as a CWE-787 out-of-bounds write in FFmpeg's MagicYUV decoder. The core Python generator, exploit/exploit_cve_2026_8461.py, constructs a malicious AVI with 1280x32 YUV420P geometry and specially chosen slice dimensions. It applies inverse left-prediction encoding so decoded chroma bytes overwrite selected heap locations. The intended exploitation chain overwrites an adjacent AVBuffer object's free callback with libc system() and its opaque argument with an in-heap command string; freeing the frame then executes the command. exploit/auto_calibrate.py supports debug-symbol builds, while auto_calibrate_nosym.py supports stripped dynamically linked builds by breaking on exported av_buffer_create and using GDB watchpoints to discover Cb-plane out-of-bounds locations, AVBuffer offsets, glibc chunk metadata, and system() addresses. The resulting JSON calibration is consumed by the AVI generator. The exploit is highly environment-specific: it requires ASLR disabled, matching allocator behavior, a matching FFmpeg/libc build, and an unchanged AVI pathname. lab/setup_lab.sh installs dependencies, clones and builds FFmpeg n8.0.1 into /usr/local, and obtains the upstream PoC. lab/prepare_payloads.sh calibrates against that local build and creates an AVI under lab/vids/. setup.sh orchestrates the lab workflow. player/main.cpp is a Qt GUI demonstration harness that sets LD_LIBRARY_PATH to /usr/local/lib and invokes the vulnerable ffmpeg decoder on a selected file. Documentation states the trigger occurs during decoding, affecting file-processing surfaces such as media players, transcoders, thumbnail generators, and upload-preview pipelines, rather than during probing alone. There are implementation inconsistencies in the wrapper lab: several references use prepare_payload.sh while the included file is prepare_payloads.sh, and player/CMakeLists.txt is empty despite compile.sh expecting a build target; these may prevent the bundled end-to-end demo scripts/player from working without correction, but do not change the apparent purpose of the core exploit scripts.
Repository contains a single Python exploit generator and a README. The main file, CVE-2026-8461.py, is a standalone Python 3 proof-of-concept/operational exploit builder for a claimed FFmpeg MagicYUV decoder out-of-bounds write vulnerability (CVE-2026-8461, 'PixelSmash'). The script constructs a minimal MagicYUV frame inside an AVI container, deliberately using SLICE_HEIGHT=31 and crafted chroma-plane data to trigger an out-of-bounds write during decoding. Its exploitation strategy is more than a crash PoC: it embeds an attacker-supplied shell command into a heap-shaped payload, preserves optional glibc metadata, and overwrites fields resembling an AVBuffer structure so that a function pointer/free callback is replaced with system() and the opaque pointer references the command buffer. The script supports target-specific calibration through a JSON file or direct CLI parameters for system() and command heap addresses, indicating an attempt at practical RCE under controlled conditions. Repository structure is minimal: README.md documents the vulnerability, impact, affected software, and mitigation; CVE-2026-8461.py is the only code file and clear entry point. No network communication, C2, or remote endpoints are present in the code; delivery is via a malicious media file, making the primary attack vector file-based against applications or services that automatically decode MagicYUV/FFmpeg content.
Repository contains a working Python-based exploit PoC for CVE-2026-8461 ('PixelSmash'), a heap out-of-bounds write in FFmpeg's MagicYUV decoder. The repo structure is straightforward: two detailed analysis documents (English and Chinese), a README with usage instructions, and three Python scripts comprising the exploit workflow. `exploit_cve_2026_8461.py` is the main payload generator that crafts a malicious AVI with MagicYUV frame geometry chosen to force a 640-byte OOB write from the Cb plane on the final slice. It uses inverse left-prediction encoding so the decoded bytes in heap memory become attacker-chosen values, then overwrites AVBuffer fields to redirect `free` to `system()` and point `opaque` at an embedded shell command string. `auto_calibrate.py` supports debug-symbol FFmpeg builds by driving GDB with source breakpoints at `magicyuv.c:291`, dumping heap-adjacent memory, locating AVBuffer structures, and extracting the `system()` address. `auto_calibrate_nosym.py` performs similar calibration for stripped dynamically linked builds by breaking on exported `av_buffer_create`, identifying Cb/Cr allocations, setting a hardware watchpoint on the expected OOB start, and reconstructing heap metadata from the dump. The exploit is not framework-based and is more than a detector: it is an operational PoC with a hardcoded exploitation strategy and customizable shell-command payload. Primary attack vector is file-based delivery of a crafted AVI to any application that fully decodes MagicYUV content via vulnerable FFmpeg/libavcodec. The README explicitly notes that probe-only paths such as `ffprobe` or `ffmpeg -i file` without output do not trigger the final execution path. Practical exploitation is constrained: tested on x86_64, depends on glibc heap layout, requires ASLR disabled, and calibration is specific to binary build, libc version, and even AVI path length. Notable fingerprintable artifacts include `/tmp/exploit.avi`, `calibration.json`, `/tmp/pwned`, the vulnerable source path `libavcodec/magicyuv.c`, and an example reverse-shell callback target `10.0.0.1:4444` embedded only as sample payload text.
Repository contains a README and a single Python exploit generator, exploit_cve_2026_8461.py. The script is not a scanner or detector; it builds crafted AVI files intended to exploit CVE-2026-8461 in FFmpeg's MagicYUV decoder. The stated exploit chain is a heap out-of-bounds write leading to corruption of an adjacent AVBuffer structure, overwriting its free callback with system() and arranging a heap-resident command string so cleanup triggers arbitrary command execution. The code structure includes helper packing/unpacking routines, left-prediction encode/decode logic to shape pixel bytes into desired post-decode memory contents, a TargetCalibration dataclass for target-specific offsets and addresses, frame-building logic for malicious MagicYUV content, AVI container construction, calibration support, and a CLI main() routine. The exploit supports two modes: a baseline crash/OOB mode and a calibrated RCE mode. The baseline mode generates a file expected to crash or corrupt memory on vulnerable FFmpeg. The RCE mode requires explicit parameters such as system() address, heap command address, AVBuffer offset, and optionally calibration JSON/glibc metadata. Operationally, the exploit is file-based: the attacker delivers a malicious AVI and waits for a local ffmpeg process to decode it. The script assumes a narrow target environment: ASLR disabled, glibc malloc allocator, calibrated heap layout, and a vulnerable unpatched FFmpeg build. Because the payload is an attacker-provided shell command but relies on hardcoded addresses and manual calibration rather than a reusable framework, the maturity is best classified as OPERATIONAL rather than WEAPONIZED.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
85 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A remotely accessible FFmpeg-related vulnerability remediated by Ubuntu USN-8750-1. The supplied CVSS v2 vector indicates low attack complexity, no authentication, and complete confidentiality, integrity, and availability impact.
A vulnerability tracked as CVE-2026-8461 affecting SUSE Linux 15 ffmpeg-related packages, addressed by SUSE advisory SUSE-SU-2026:3632-1.
A heap out-of-bounds write vulnerability in FFmpeg's libavcodec MagicYUV decoder that may allow weaponized media files and possible remote code execution.
Heap out-of-bounds write vulnerability in FFmpeg's MagicYUV decoder caused by incorrect chroma slice height handling, potentially leading to denial of service and, under constrained conditions such as disabled ASLR or with an additional info leak, remote code execution via malicious AVI/MKV/MOV media files.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.