vLLM dynamic processor configuration has remote code execution risk
Start here
A GitHub security advisory disclosed that vLLM's dynamic auto_map.AutoProcessor path has a remote code execution risk: when the operator enables --trust-remote-code and an attacker can control a revision of the served model repository, a request can cause the service to import the processor Python code from that revision; the server also needs to be able to fetch or have cached that revision. The default trust_remote_code=False is not affected. The advisory notes that /tokenize is not protected by vLLM's API key.
Generated by AI from reports · Updated 2 days ago
Progress timeline
- GitHub 安全公告SelectedvLLM discloses remote code execution vulnerability under dynamic processor configuration
vLLM's dynamic auto_map.AutoProcessor path has a remote code execution risk: when the operator enables --trust-remote-code, and an attacker can control a revision of the served model repository, a request can cause the service to import the processor Python code for that revision. The server also needs to be able to fetch or have cached that revision; the default trust_remote_code=False is not affected. The advisory notes that /tokenize is not protected by vLLM's API-key routing authentication and requires additional access control. The GitHub advisory marks affected versions as >= 0.7.3, < 0.31.0, with the fix in version 0.31.0.
Related discussion
Attention trend
New sources per day
- Oct 8New1 sources (1 outlets,0 accounts)
- Oct 9New0 sources (0 outlets,0 accounts)
- Oct 10New0 sources (0 outlets,0 accounts)
- Oct 11New0 sources (0 outlets,0 accounts)
- Oct 12New0 sources (0 outlets,0 accounts)
- Oct 13New0 sources (0 outlets,0 accounts)