vllm
Affected
- introduced
0, fixed0.8.0(ecosystem)
Fixed versions
0.8.0
Fix
- Fixed version
0.8.0pip install --upgrade vllm==0.8.0
Advisory
Also known as: None
CVE-2025-24357 Malicious model remote code execution fix bypass with PyTorch < 2.6.0
Description
https://github.com/vllm-project/vllm/security/advisories/GHSA-rh4j-5rhw-hr54 reported a vulnerability where loading a malicious model could result in code execution on the vllm host. The fix applied to specify weights_only=True to calls to torch.load() did not solve the problem prior to PyTorch 2.6.0.
PyTorch has issued a new CVE about this problem: https://github.com/advisories/GHSA-53q9-r3pm-6pq6
This means that versions of vLLM using PyTorch before 2.6.0 are vulnerable to this problem.
Background Knowledge
When users install VLLM according to the official manual
image
But the version of PyTorch is specified in the requirements. txt file
image
So by default when the user install VLLM, it will install the PyTorch with version 2.5.1
image
In CVE-2025-24357, weights_only=True was used for patching, but we know this is not secure.
Because we found that using Weights_only=True in pyTorch before 2.5.1 was unsafe
Here, we use this interface to prove that it is not safe.
image
Fix
update PyTorch version to 2.6.0
Credit
This vulnerability was found By Ji'an Zhou and Li'shuo Song
Critical Basis: The source's own band: CRITICAL
0, fixed 0.8.0 (ecosystem)0.8.0
0.8.0pip install --upgrade vllm==0.8.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: GitHub Advisory Database (reviewed advisories) · CC BY 4.0