GHSA-ggpf-24jw-3fcw json
CVE-2025-24357 Malicious model remote code execution fix bypass with PyTorch < 2.6.0
published last yr. modified 3mo ago
- cvss
- 9.8
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
## 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 
But the version of PyTorch is specified in the requirements. txt file 
So by default when the user install VLLM, it will install the PyTorch with version 2.5.1 
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. 
## Fix update PyTorch version to 2.6.0
## Credit This vulnerability was found By Ji'an Zhou and Li'shuo Song
Patch / fix
- pypi vllm 0.8.0
Is GHSA-ggpf-24jw-3fcw in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | vllm | <0.8.0 |
0.8.0 |
Classification
- Weakness
-
- CWE-1395 Dependency on Vulnerable Third-Party Component
References
Sources
- GitHub Advisory GHSA-ggpf-24jw-3fcw
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.