vLLM up to 0.11.0 Completions API Endpoint torch.load input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in vLLM up to 0.11.0. The impacted element is the function torch.load of the component Completions API Endpoint. Such manipulation leads to input validation.
This vulnerability is listed as CVE-2025-62164. The attack may be performed from remote. There is no available exploit.
The affected component should be upgraded.
Details
A vulnerability was found in vLLM up to 0.11.0. It has been rated as critical. Affected by this issue is the function torch.load of the component Completions API Endpoint. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is confidentiality, integrity, and availability. CVE summarizes:
vLLM is an inference and serving engine for large language models (LLMs). From versions 0.10.2 to before 0.11.1, a memory corruption vulnerability could lead to a crash (denial-of-service) and potentially remote code execution (RCE), exists 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 to_dense(). This memory corruption can crash vLLM and potentially lead to code execution on the server hosting vLLM. This issue has been patched in version 0.11.1.
The advisory is available at github.com. This vulnerability is handled as CVE-2025-62164 since 10/07/2025. The exploitation is known to be easy. The attack may be launched remotely. Technical details are known, but there is no available exploit.
Upgrading to version 0.11.1 eliminates this vulnerability.
The vulnerability is also documented in the databases at EUVD (EUVD-2025-198314) and CERT Bund (WID-SEC-2025-2666). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Affected
- Open Source vllm
- Open Source PyTorch
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.8
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: vLLM 0.11.1
Timeline
10/07/2025 CVE reserved11/21/2025 Advisory disclosed
11/21/2025 VulDB entry created
01/09/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2025-62164 (🔒)
GCVE (CVE): GCVE-0-2025-62164
GCVE (VulDB): GCVE-100-333098
EUVD: 🔒
CERT Bund: WID-SEC-2025-2666 - vllm und PyTorch: Schwachstelle ermöglicht DoS und potenzielle Codeausführung
Entry
Created: 11/21/2025 03:16Updated: 01/09/2026 18:31
Changes: 11/21/2025 03:16 (63), 11/24/2025 13:18 (7), 01/09/2026 18:31 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.