Skip to content

AAK-MCP-FFMPEG-CVE-2026-117568-001: mcp-ffmpeg from 1.0.3: video paths reach a shell command string

Severity
HIGH
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
McpFfmpegPathShellInjection

What it detects

mcp-ffmpeg (npm mcp-ffmpeg, bitscorp-mcp/mcp-ffmpeg), an MCP server for FFmpeg, builds the commands its resize-video, extract-audio and get-video-info tools run by placing the videoPath and outputDir parameters inside a double-quoted string handed to child_process.exec. A path holding $(), backticks or a closing double quote, which an existing file or directory name can carry, breaks out of the string, so a client or a prompt-injected agent that can name a file runs commands as the server's user (CVE-2026-117568, CVSS 7.0, CWE-78). Checked in the published npm packages: the MCP server first ships in 1.0.3 (1.0.0 to 1.0.2 are an Express upload service on fluent-ffmpeg with no MCP tools), and 1.0.5, the newest release (2025-03-13), still builds ffmpeg -i "${absVideoPath}" ... strings. bitscorp-mcp/mcp-ffmpeg#8 is open and there is no fixed release.

How to fix

Remove mcp-ffmpeg from agents that read untrusted content, or run it as a user that can reach nothing worth taking; there is no fixed release. A fork that passes FFmpeg its arguments as an array (execFile, or spawn without a shell) closes the injection.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-FFMPEG-CVE-2026-117568-001

Limitations

Reports an npm reference to mcp-ffmpeg from 1.0.3: a package.json or lockfile entry, the package an npx launch in an MCP config names, or a config that runs a global install by that bare name. Presence-only from 1.0.3: every later version is reported, a future fixed one included, until the pin gets a floor, and so is a reference that states no version, which installs 1.0.5. 1.0.0 to 1.0.2 had no MCP tools and are not reported. PyPI's mcp-ffmpeg (priyanshum143/MCP-FFMPEG) is another project, so a Python requirement and a uvx launch are not matched. It reads the name and version, not which tools the client lets the model call. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-FFMPEG-CVE-2026-117568-001.md: the page then shows that text, with the registry reference appended under it.