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.
The product does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission.
| Link | Tags |
|---|---|
| https://github.com/vllm-project/vllm/security/advisories/GHSA-rm76-4mrf-v9r8 | vendor advisory |
| https://github.com/vllm-project/vllm/pull/12621 | issue tracking |
| https://github.com/python/cpython/commit/432117cd1f59c76d97da2eaff55a7d758301dbc7 | not applicable |