CVE-2025-25183

vLLM using built-in hash() from Python 3.12 leads to predictable hash collisions in vLLM prefix cache

State
Published
Severity
2.6 Low
Published
Feb 7, 2025
Updated
Feb 12, 2025
Reserved
Feb 3, 2025

Read the record on cve.org

Description

vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. Maliciously constructed statements can lead to hash collisions, resulting in cache reuse, which can interfere with subsequent responses and cause unintended behavior. Prefix caching makes use of Python's built-in hash() function. As of Python 3.12, the behavior of hash(None) has changed to be a predictable constant value. This makes it more feasible that someone could try exploit hash collisions. The impact of a collision would be using cache that was generated using different content. Given knowledge of prompts in use and predictable hashing behavior, someone could intentionally populate the cache using a prompt known to collide with another prompt in use. This issue has been addressed in version 0.7.2 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Scores

CVSSScoreVectorSource
3.12.6 LowCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:NGitHub_M

Weaknesses

  • CWE-354 Improper Validation of Integrity Check Value

Affected Products

ProductVersions
vllmvllm-project
  • < 0.7.2Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.