CVE-2026-47155: vllm · Insufficient Verification of Data Authenticity
Affects vllmSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 0.22.0 when convenient.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.22.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade vllm and vllm-project/vllm to 0.22.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vllm-projectvllm | Affected
| Fixed in
|
GitHubvllm-project/vllmpkg:github/vllm-project/vllmOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade vLLM to version 0.22.0 or later, where the revision pinning controls are properly enforced for all model artifacts. No other official remediation or temporary fix is documented. Patch status is confirmed by the vendor advisory stating the issue is fixed in 0.22.0.
Description
vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.22.0, vLLM's revision pinning controls do not consistently apply to all artifacts loaded for a model. A deployment that supplies --revision or --code-revision can still load dynamic code, GGUF files, image processors, retrieval side weights, or same-repository subfolder weights/config from an unpinned/default revision. This is a supply-chain integrity issue for pinned vLLM deployments. Operators can believe they are serving a reviewed model revision while vLLM resolves behavior-affecting nested or sibling artifacts outside that reviewed revision. This vulnerability is fixed in 0.22.0.
References
- github.com/vllm-project/vllm/security/advisories/GHSA-3ww4-5jv9-j5gm (opens in a new tab)
- github.com/vllm-project/vllm/pull/42616 (opens in a new tab)
- github.com/vllm-project/vllm/commit/d26a28ab033697f55a1414b5b0435de7cd6045b6 (opens in a new tab)
- huntr.com/bounties/3f1e24c0-87d2-4f6c-a705-820f380879ac (opens in a new tab)