Chainvllm-project · vllmPyPI:vllm
vllm-project vllm: incomplete fixes (2025–2026)
3 CVEs over 2 generations, 1 Dec 2025 to 28 May 2026.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2025-664481 Dec 2025 First in the chain
- CVE-2026-2280721 Jan 2026 No direct link to an earlier CVE
- CVE-2026-494428 May 2026 incomplete fix for CVE-2025-66448incomplete fix for CVE-2026-22807
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2025-66448 | 1 Dec 2025 | vLLM vulnerable to remote code execution via transformers_utils/get_config · fixed in 0.11.1 | First in chain | 15.3 |
| CVE-2026-22807 | 21 Jan 2026 | vLLM affected by RCE via auto_map dynamic module loading during model initialization · fixed in 0.14.0 | First in chain | 23.6 |
| CVE-2026-4944 | 28 May 2026 | Hardcoded trust_remote_code=True in vllm-project/vllm Bypasses User Security Control | CVE-2025-66448 · incomplete fix · High | 17.1 |