INCIDENT MAP

Browse / Unsafe Model Loading and Supply Chain / GHSA-ggpf-24jw-3fcw

CVE-2025-24357 Malicious model remote code execution fix bypass with PyTorch < 2.6.0

GHSA-ggpf-24jw-3fcw ยท 2025-04-23 critical

Class
Unsafe Model Loading and Supply Chain (filed by a model that read the advisory)
Technique
Code and command execution
Affected
vllm (PyPI)
Gets past
Safe model loader or scanner
CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

How it works, in short

A malicious checkpoint still executes code when loaded with weights-only mode on PyTorch versions before 2.6, so the vLLM safeguard is ineffective. (Our summary, written by a model. The source text is below.)

Details

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

References

Source: GitHub Advisory Database, used under CC BY 4.0.