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.
CVE-2026-47155
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EPSS
- 4.3%
- KEV
- Not listed
Published
June 10, 2026
Last Modified
June 24, 2026
Advisory Details (4)
Auto-updated Jun 23, 2026huntr - The world's first bug bounty platform for AI/ML
https://huntr.com/bounties/3f1e24c0-87d2-4f6c-a705-820f380879accommit d26a28ab0336 (vllm-project/vllm)
Fix landed in vllm-project/vllm commit d26a28ab0336 — awaiting tagged release
https://github.com/vllm-project/vllm/commit/d26a28ab033697f55a1414b5b0435de7cd6045b6fix: propagate revision/code_revision pins to all artifact boundaries
Fix merged in vllm-project/vllm PR #42616 on 2026-05-15 — awaiting tagged release
https://github.com/vllm-project/vllm/pull/42616Artifact Pin Decay in vLLM allows pinned deployments to load unpinned code, weights, and processors · Advisory · vllm-project/vllm · GitHub
https://github.com/vllm-project/vllm/security/advisories/GHSA-3ww4-5jv9-j5gmVendor Advisories for CVE-2026-47155(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| vllm | 0.0.1 ... 0.9.2 (86 versions) | 0.22.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 45× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-07 06:12 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 11:12 UTCEG score recompute
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 11:43 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 08:01 UTCEG score recompute
- 2026-07-02 07:19 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 08:08 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 08:56 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 09:46 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 10:35 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 11:25 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 12:15 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 07:09 UTCEG score recompute
- 2026-06-24 14:05 UTCEPSS rescore
Show 20 moreShow fewer
- 2026-06-24 07:58 UTCEG score recompute
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 08:41 UTCEG score recompute
- 2026-06-22 09:29 UTCEG score recompute
- 2026-06-21 10:05 UTCEG score recompute
- 2026-06-20 09:45 UTCEG score recompute
- 2026-06-19 10:28 UTCEG score recompute
- 2026-06-18 11:03 UTCEG score recompute
- 2026-06-17 11:30 UTCEG score recompute
- 2026-06-16 12:21 UTCEG score recompute
- 2026-06-15 13:09 UTCEG score recompute
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-14 13:58 UTCEG score recompute
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 14:48 UTCEG score recompute
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 15:38 UTCEG score recompute
- 2026-06-11 16:27 UTCEG score recompute
- 2026-06-10 17:17 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-345
Frequently asked(5)
What is CVE-2026-47155?
When was CVE-2026-47155 disclosed?
Is CVE-2026-47155 actively exploited?
What is the CVSS score of CVE-2026-47155?
How do I remediate CVE-2026-47155?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47155
Is Your Infrastructure Affected by CVE-2026-47155?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.