GHSA-mrw7-hf4f-83pf: Input Validation
Summary A memory corruption vulnerability that leading to a crash (denial-of-service) and potentially remote code execution (RCE) exists in vLLM versions 0.10.2 and later, in the Completions API endpoint. When processing user-supplied prompt embeddings, the endpoint loads serialized tensors using torch.load() without sufficient validation.
Due to a change introduced in PyTorch 2.8.0, sparse tensor integrity checks are disabled by default. As a result, maliciously crafted tensors can bypass internal bounds checks and trigger an out-of-bounds memory write during the call to todense(). This memory corruption can crash vLLM and potentially lead to code execution on the server hosting vLLM.
Details A vulnerability that can lead to RCE from the completions API endpoint exists in vllm, where due to missing checks when loading user-provided tensors, an out-of-bounds write can be triggered. This happens because the default behavior of torch.load(tensor, weightsonly=True) since pytorch 2.8.0 is to not perform validity checks for sparse tensors, and this needs to be enabled explicitly using the torch.sparse.checksparsetensorinvariants context manager.
The vulnerability is in the following code in vllm/entrypoints/renderer.py:148
python def loadandvalidateembed(embed: bytes) -> EngineEmbedsPrompt: tensor = torch.load( io.BytesIO(pybase64.b64decode(embed, validate=True)), weightsonly=True, maplocation=torch.device("cpu"), ) assert isinstance(tensor, torch.Tensor) and tensor.dtype in ( torch.float32, torch.bfloat16, torch.float16, ) tensor = tensor.todense()
Because of the missing checks, loading invalid prompt embedding tensors provided by the user can cause an out-of-bounds write in the call to todense .
Impact All users with access to this API are able to exploit this vulnerability. Unsafe deserialization of untrusted input can be abused to achieve DoS and potentially remote code execution (RCE) in the vLLM server process. This impacts deployments running vLLM as a server or any instance that deserializes untrusted/model-provided payloads.
Fix
https://github.com/vllm-project/vllm/pull/27204
Acknowledgements
Finder: AXION Security Research Team (Omri Fainaro, Bary Levy): discovery and coordinated disclosure.
Affected Software
Event History
Frequently Asked Questions
What is the severity of GHSA-mrw7-hf4f-83pf?
GHSA-mrw7-hf4f-83pf is considered a high severity vulnerability due to its potential for remote code execution and denial-of-service.
How do I fix GHSA-mrw7-hf4f-83pf?
To fix GHSA-mrw7-hf4f-83pf, upgrade to vLLM version 0.11.1 or later.
Which versions are affected by GHSA-mrw7-hf4f-83pf?
Versions of vLLM from 0.10.2 to 0.11.0 are affected by GHSA-mrw7-hf4f-83pf.
What types of attacks can GHSA-mrw7-hf4f-83pf enable?
GHSA-mrw7-hf4f-83pf can enable denial-of-service attacks and potentially allow for remote code execution.
What component of vLLM does GHSA-mrw7-hf4f-83pf impact?
GHSA-mrw7-hf4f-83pf impacts the Completions API endpoint of vLLM.