UTC
Medium

Crafted IAMF audio upload reaches a PyAV/FFmpeg native heap overflow through the speech transcription path — denial of service

GHSA-m52c-39rh-f3gp · published 2026-09-28

Severity
Medium
CVSS score
6.5
Chance of exploitation (EPSS)
No CVE
Fixed in
0.29.0
What it is

An attacker who can reach /v1/audio/transcriptions on an affected deployment can crash the vLLM API process by uploading a crafted IAMF container. The preconditions are that the audio path falls back to PyAV (i.e. soundfile is unavailable or cannot parse the container) and the linked libavformat is within the vulnerable IAMF range. No authentication beyond ordinary request access is required. The effect is request-controlled native heap corruption in the speech-processing process, leading to process death and denial of service for every user of that server. The evidence proves allocator corruption and service death (availability). …

What to do

Upgrade vllm to 0.29.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Reject PyAV container parsing before any av.open() call when the linked libavformat build falls within the vulnerable IAMF range. Raise the default PyAV/FFmpeg dependency floor to a wheel line that bundles fixed FFmpeg releases (out of the vulnerable IAMF range) across the CUDA, CPU, and ROCm requirement sets. Apply the same pre-open guard to the request-selectable PyAV video backend so a caller cannot bypass the audio-path fix through a sibling media route. Coordinate disclosure with FFmpeg/PyAV for the underlying native parser bug if a CVE is not already assigned; the true root fix belongs upstream in FFmpeg, with the vLLM-side fix being input gating plus the dependency-floor bump. …

Affected
PackageRegistryAffectedFixed in
vllmPyPI< 0.29.00.29.0

The impact, patch and workaround text comes from the advisory, shortened (published by vLLM). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].