vLLM has a Weakness in MultiModalHasher Image Hashing Implementation
Published 28 May 2025 · Updated 7 Aug 2026
Is your project on an affected vllm?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=0.7.0 <0.9.0
- Fixed in
- 0.9.0
pip install 'vllm>=0.9.0'Details
Summary
In the file vllm/multimodal/hasher.py, the MultiModalHasher class has a security and data integrity issue in its image hashing method. Currently, it serializes PIL.Image.Image objects using only obj.tobytes(), which returns only the raw pixel data, without including metadata such as the image’s shape (width, height, mode). As a result, two images of different sizes (e.g., 30x100 and 100x30) with the same pixel byte sequence could generate the same hash value. This may lead to hash collisions, incorrect cache hits, and even data leakage or security risks.
Details
- Affected file:
vllm/multimodal/hasher.py - Affected method:
MultiModalHasher.serialize_item
https://github.com/vllm-project/vllm/blob/9420a1fc30af1a632bbc2c66eb8668f3af41f026/vllm/multimodal/hasher.py#L34-L35
- Current behavior: For
Image.Imageinstances, onlyobj.tobytes()is used for hashing. - Problem description:
obj.tobytes()does not include the image’s width, height, or mode metadata. - Impact: Two images with the same pixel byte sequence but different sizes could be regarded as the same image by the cache and hashing system, which may result in:
- Incorrect cache hits, leading to abnormal responses
- Deliberate construction of images with different meanings but the same hash value
Recommendation
In the serialize_item method, serialization of Image.Image objects should include not only pixel data, but also all critical metadata—such as dimensions (size), color mode (mode), format, and especially the info dictionary. The info dictionary is particularly important in palette-based images (e.g., mode 'P'), where the palette itself is stored in info. Ignoring info can result in hash collisions between visually distinct images with the same pixel bytes but different palettes or metadata. This can lead to incorrect cache hits or even data leakage.
Summary:
Serializing only the raw pixel data is insecure. Always include all image metadata (size, mode, format, info) in the hash calculation to prevent collisions, especially in cases like palette-based images.
Impact for other modalities For the influence of other modalities, since the video modality is transformed into a multi-dimensional array containing the length, width, time, etc. of the video, the same problem exists due to the incorrect sequence of numpy as well.
For audio, since the momo function is not enabled in librosa.load, the loaded audio is automatically encoded into single channels by librosa and returns a one-dimensional array of numpy, thus keeping the structure of numpy fixed and not affected by this issue.
Fixes
- https://github.com/vllm-project/vllm/pull/17378
Is GHSA-c65p-x677-fgj6 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected vllm, and gives you the command that fixes it.
More advisories for vllm
- LowCVE-2026-115917vLLM: Permissive default CORS origins allow cross-origin requests to the vLLM HTTP server · 28 Oct 2026
- MediumCVE-2026-115913vLLM: Phi-4 multimodal audio encoder materializes and retains full attention matrices: a single max-length audio OOM-crashes the vLLM engine · 28 Oct 2026
- MediumCVE-2026-115914vLLM DeepSeek-OCR image processing vulnerable to denial of service · 28 Oct 2026
- HighCVE-2026-115915vLLM: Untrusted EPS inputs can trigger denial of service or Ghostscript RCE · 28 Oct 2026
- HighCVE-2026-115912vLLM: Public multimodal SHM handle forgery reaches worker-side `pickle.loads()` with insecure serialization disabled · 28 Oct 2026
- MediumCVE-2026-115916vLLM: Out-of-vocabulary prompt token id passes input validation and triggers a CUDA device-side assert (engine crash / DoS) · 28 Oct 2026
References
- Linkgithub.com/vllm-project/vllm/security/advisories/GHSA-c65p-x677-fgj6
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-46722
- Linkgithub.com/vllm-project/vllm/pull/17378
- Linkgithub.com/vllm-project/vllm/commit/99404f53c72965b41558aceb1bc2380875f5d848
- Linkgithub.com/pypa/advisory-database/tree/main/vulns/vllm/PYSEC-2025-43.yaml
- Packagegithub.com/vllm-project/vllm
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.