
The FFmpeg 9.0.2 CVE list is mostly unreachable. Two aren't.
The FFmpeg 9.0.2 CVE batch from November 9, 2026: which bugs need a crafted file, which fire on normal transcodes, and what to patch when no 9.0.3 exists.
8 articles about security.

The FFmpeg 9.0.2 CVE batch from November 9, 2026: which bugs need a crafted file, which fire on normal transcodes, and what to patch when no 9.0.3 exists.

CVE-2026-117568 turns mcp-ffmpeg command injection into RCE: a filename with $() runs as your server. The two real fixes, and the safer shape for agents.

The ffmpeg Brotli CVE (CVE-2026-111497) reaches FFmpeg through libjxl and JPEG XL brob boxes. How to check your build and what to block at ingest right now.

FFmpeg CVE October 2026: CVE-2026-107676 and CVE-2026-107678 fire on the uploaded file, and no patched release exists. The mitigations that work today.

The ffmpeg protocol whitelist bypass (CVE-2026-107697) and the Oct 8, 2026 CVE batch: which bugs are fixed in 8.1.3, which have no release, and how to harden.

n8n CVE October 2026: patch to 1.123.76, 2.37.7, or 2.38.2, what each flaw allows, NODES_EXCLUDE mitigations, and how to upgrade without breaking FFmpeg.

FFmpeg CVE-2026-96611 affects every build before 9.0. How to check the version your pipeline actually runs, who's exposed, and how to patch a container.

Securely transcode video with an API. HTTPS-only endpoints, Bearer token auth, presigned uploads, and zero persistent storage. No FFmpeg server to patch.