CVE-2025-25183: Vllm VLLM Uses Python 3.12 Built-in Vulnerability
LOWCVE-2025-25183 is a LOW (CVSS 2.6) vllm uses python 3.12 built-in vulnerability (CWE-354: Improper Validation of Integrity Check Value) affecting Vllm libraries in the PyPI ecosystem. The issue involves vllm uses python 3.12 built-in hash() which leads to predictable hash collisions in prefix cache. Remediation is available by upgrading affected packages to version 0.7.2.
CVE-2025-25183 at a Glance
Security Impact
CVSS: 2.6
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N).
How to Fix CVE-2025-25183
To remediate this vulnerability, upgrade all affected Vllm dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install vllm>=0.7.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show vllm
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2025-25183, inspect your installed packages using pip:
pip show vllm
Analyze the terminal output to locate any version of Vllm in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.7.2), your application is affected.
Note: The pip show vllm command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-354: Improper Validation of Integrity Check Value, where 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. In Vllm, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-25183 Affected Vllm Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
vllm
|
PyPI |
< 0.7.2
|
0.7.2
|
References
Frequently Asked Questions
What is CVE-2025-25183?
Which Vllm versions are affected?
What version fixes CVE-2025-25183?
Is vllm affected?
What is the CVSS score of CVE-2025-25183?
What CWE is associated with CVE-2025-25183?
How can I check PyPI dependencies for CVE-2025-25183?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-rm76-4mrf-v9r8",
"modified" : "2025-07-02T14:20:34Z",
"published" : "2025-02-06T20:00:05Z",
"aliases" : [ "CVE-2025-25183" ],
"summary" : "vLLM uses Python 3.12 built-in hash() which leads to predictable hash collisions in prefix cache",
"details" : "### Summary\n\nMaliciously constructed prompts can lead to hash collisions, resulting in prefix cache reuse, which can interfere with subsequent responses and cause unintended behavior.\n\n### Details\n\nvLLM's 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.\n\n### Impact\n\nThe 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. \n\n### Solution\n\nWe address this problem by initializing hashes in vllm with a value that is no longer constant and predictable. It will be different each time vllm runs. This restores behavior we got in Python versions prior to 3.12.\n\nUsing a hashing algorithm that is less prone to collision (like sha256, for example) would be the best way to avoid the possibility of a collision. However, it would have an impact to both performance and memory footprint. Hash collisions may still occur, though they are no longer straight forward to predict.\n\nTo give an idea of the likelihood of a collision, for randomly generated hash values (assuming the hash generation built into Python is uniformly distributed), with a cache capacity of 50,000 messages and an average prompt length of 300, a collision will occur on average once every 1 trillion requests.\n\n### References\n\n* https://github.com/vllm-project/vllm/pull/12621\n* https://github.com/python/cpython/commit/432117cd1f59c76d97da2eaff55a7d758301dbc7\n* https://github.com/python/cpython/pull/99541",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "vllm"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.7.2"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/vllm-project/vllm/security/advisories/GHSA-rm76-4mrf-v9r8"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-25183"
}, {
"type" : "WEB",
"url" : "https://github.com/python/cpython/pull/99541"
}, {
"type" : "WEB",
"url" : "https://github.com/vllm-project/vllm/pull/12621"
}, {
"type" : "WEB",
"url" : "https://github.com/python/cpython/commit/432117cd1f59c76d97da2eaff55a7d758301dbc7"
}, {
"type" : "WEB",
"url" : "https://github.com/vllm-project/vllm/commit/73b35cca7f3745d07d439c197768b25d88b6ab7f"
}, {
"type" : "WEB",
"url" : "https://github.com/pypa/advisory-database/tree/main/vulns/vllm/PYSEC-2025-62.yaml"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/vllm-project/vllm"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-354" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2025-02-06T20:00:05Z",
"nvd_published_at" : "2025-02-07T20:15:34Z"
}
}