CVE-2025-66448: vLLM vulnerable to remote code execution via transformers_utils/get_config
(updated )
vllm has a critical remote code execution vector in a config class named Nemotron_Nano_VL_Config. When vllm loads a model config that contains an auto_map entry, the config class resolves that mapping with get_class_from_dynamic_module(...) and immediately instantiates the returned class. This fetches and executes Python from the remote repository referenced in the auto_map string. Crucially, this happens even when the caller explicitly sets trust_remote_code=False in vllm.transformers_utils.config.get_config. In practice, an attacker can publish a benign-looking frontend repo whose config.json points via auto_map to a separate malicious backend repo; loading the frontend will silently run the backend’s code on the victim host.
References
- github.com/advisories/GHSA-8fr4-5q9j-m8gm
- github.com/pypa/advisory-database/tree/main/vulns/vllm/PYSEC-2026-2015.yaml
- github.com/vllm-project/vllm
- github.com/vllm-project/vllm/commit/ffb08379d8870a1a81ba82b72797f196838d0c86
- github.com/vllm-project/vllm/pull/28126
- github.com/vllm-project/vllm/security/advisories/GHSA-8fr4-5q9j-m8gm
- nvd.nist.gov/vuln/detail/CVE-2025-66448
- pypi.org/project/vllm
Code Behaviors & Features
Detect and mitigate CVE-2025-66448 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →