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
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). …
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. …
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| vllm | PyPI | < 0.29.0 | 0.29.0 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalvLLM: OpenAI auth bypassvllm
- CriticalvLLM has RCE In Video Processingvllm
- CriticalvLLM Allows Remote Code Execution via PyNcclPipe Communication Servicevllm
- CriticalvLLM Vulnerable to Remote Code Execution via Mooncake Integrationvllm
- CriticalCVE-2025-24357 Malicious model remote code execution fix bypass with PyTorch < 2.6.0vllm
- CriticalvLLM Deserialization of Untrusted Data vulnerabilityvllm
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.