vllm
Affected
- introduced
0.10.1, fixed0.14.0(ecosystem)
Fixed versions
0.14.0
Fix
- Fixed version
0.14.0pip install --upgrade vllm==0.14.0
Advisory
Also known as: CVE-2026-22807, GHSA-2pc9-4j83-qjmr
vLLM affected by RCE via auto_map dynamic module loading during model initialization
Summary
vLLM loads Hugging Face auto_map dynamic modules during model resolution without gating on `trust_remote_code`, allowing attacker-controlled Python code in a model repo/path to execute at server startup.
---
Impact
An attacker who can influence the model repo/path (local directory or remote Hugging Face repo) can achieve arbitrary code execution on the vLLM host during model load.
This happens before any request handling and does not require API access.
---
Affected Versions
All versions where vllm/model_executor/models/registry.py resolves auto_map entries with try_get_class_from_dynamic_module without checking `trust_remote_code` (at least current main).
---
Details
During model resolution, vLLM unconditionally iterates auto_map entries from the model config and calls try_get_class_from_dynamic_module, which delegates to Transformers’ get_class_from_dynamic_module and executes the module code.
This occurs even when trust_remote_code is false, allowing a malicious model repo to embed code in a referenced module and have it executed during initialization.
Relevant code
vllm/model_executor/models/registry.py:856 — auto_map resolution vllm/transformers_utils/dynamic_module.py:13 — delegates to get_class_from_dynamic_module, which executes code---
Fixes
Credits
Reported by bugbunny.ai
High Basis: CVSS v3 score 8.8, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
0.10.1, fixed 0.14.0 (ecosystem)0.14.0
0.14.0pip install --upgrade vllm==0.14.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0