CVE-2025-62164: vllm-project vllm Improper Input Validation
Vulnerability summary
CVE-2025-62164 is a high (CVSS 8.8) Improper Input Validation vulnerability in vllm-project vllm. EPSS estimates a 0.93% chance of exploitation in the next 30 days, higher than 59.9% of scored vulnerabilities.
Advisory lineage
Upstream 0 · Downstream 0 · Related 1Timeline
- 21-11-2025PublishedVulnerability first disclosed.
- 24-11-2025Last modifiedVulnerability information updated.
Description
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.
CVSS metrics
4 scores · 4 sources · 1 version- OSV · PypiEcosystem advisory · calculated8.8HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- OSV · ChainguardEcosystem advisory · calculated8.8HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- NVDNIST8.8HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS trend
Probability
0.93%
Chance of exploitation in the next 30 days
Percentile
60%
Versus all other CVEs
30-day change
+0.04 pp
From 0.89% on 20-09-2026
Known exploited
Compare KEV catalogsNot in any of the 3 tracked catalogs.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root cause- CWE-20Improper Input ValidationThe 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.
- CWE-123Write-what-where ConditionAny condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow.
- CWE-502Deserialization of Untrusted DataThe product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
- CWE-787Out-of-bounds WriteThe product writes data past the end, or before the beginning, of the intended buffer.
Affected systems
Chainguard1 product
- tritonserver-backend-vllm-meta-cuda-12.9< 25.9.0_git20251112-r1
PyPI1 product
- vllm≥ 0.10.2, < 0.11.1
Vllm1 product
- vllm≥ 0.10.2, < 0.11.1 | 0.11.1:rc0 | 0.11.1:rc1
Vllm-project1 product
- vllm≥ 0.10.2, < 0.11.1
4 vendors · 4 products
References
9 links- github.com/vllm-project/vllm/security/advisories/GHSA-mrw7-hf4f-83pfX Refsource CONFIRMWEBAdvisoryIssue TrackingVendor Advisory
- github.com/vllm-project/vllm/commit/58fab50d82838d5014f4a14d991fdb9352c9c84bX Refsource MISCWEBFIXPatch
- github.com/vllm-project/vllmPACKAGE