CVE-2025-66448 – vLLM vulnerable to remote code execution via transformers_utils/get_config

The following table lists the changes that have been made to the
CVE-2025-66448 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution
of a vulnerability, and for identifying the most recent changes that may
impact the vulnerability’s severity, exploitability, or other characteristics.

  • New CVE Received
    by [email protected]

    Dec. 01, 2025

    Action Type Old Value New Value
    Added Description vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.11.1, 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. This vulnerability is fixed in 0.11.1.
    Added CVSS V3.1 AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
    Added CWE CWE-94
    Added Reference https://github.com/vllm-project/vllm/commit/ffb08379d8870a1a81ba82b72797f196838d0c86
    Added Reference https://github.com/vllm-project/vllm/pull/28126
    Added Reference https://github.com/vllm-project/vllm/security/advisories/GHSA-8fr4-5q9j-m8gm
Share the Post:

Related Posts