Servers and applications
CVE-2026-47155
Artifact Pin Decay in vLLM allows pinned deployments to load unpinned code, weights, and processors
- Severity
- Medium 6.5
- Published
- 10 Jun 2026
- Last changed
- 25 Oct 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 0.22.0
- Exploit chance
- 0.2% in the next 30 daysHigher than 16% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Only under certain conditions · No login needed · No user action needed
- Attacker can
- Read some data · Change data
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N- Also known as
- GHSA-3ww4-5jv9-j5gm
- Sources
- NVD, Project advisories (GitHub)
Description
Originally filed via huntr: https://huntr.com/bounties/3f1e24c0-87d2-4f6c-a705-820f380879ac The vllm maintainer (Russell Bryant) redirected to this private GHSA channel. Offline proof bundle (vllm_artifact_pin_decay_bundle_verify.py + bundle-verification-20260430T143506Z.json) available on request.
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.
The expected invariant is:
Affected software
| Software | Affected versions |
|---|---|
vLLMServers and applications · cpe:a:vllm:vllm |
|
vLLMServers and applications · github:vllm-project/vllm |
|
About vLLM
open-source software for large language model inference
- Docker Hub pulls
- 44,195,225Docker Hub, 15 Nov 2026
- GitHub stars
- 96,943GitHub, 15 Nov 2026
- Forks
- 24,836GitHub, 15 Nov 2026
- Latest release
- v0.33.0rc3GitHub, 15 Nov 2026
- Released
- 2 Nov 2026GitHub
- License
- Apache Software License 2.0Wikidata
- First published on GitHub
- 9 Feb 2023GitHub
Website Source code Docker image
Vulnerabilities in vLLM
- In our list
- 169
- Published in the last 12 months
- 150
- Critical, last 12 months
- 6
- High, last 12 months
- 63
- Known exploited
- 0
- CVE-2026-130686vLLM 0.6.0 before 0.33.0 Resource Exhaustion via Multi-Image RequestsHigh 8.7 18 Nov 2026
- CVE-2026-130684vLLM before 0.33.0 Path Traversal via speculators_config verifier.name_or_pathMedium 5.3 18 Nov 2026
- CVE-2026-130685vLLM 0.28.0 before 0.33.0 Unauthenticated DoS via Out-of-Range Prompt Token IDHigh 8.7 18 Nov 2026
- GHSA-xgh8-qwjh-q853/v1/systemone bypasses the --trust-request-chat-template gateMedium 6.5 18 Nov 2026
- CVE-2026-129356vllm-project vllm Common Prefix single_type_kv_cache_manager.py race conditionLow 2.3 15 Nov 2026
- CVE-2026-126394vLLM 0.30.0 before 0.31.0 Resource Exhaustion via OpenPangu Video Backend num_framesMedium 6.9 13 Nov 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-47155
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-47155
- GitHub Advisory Database https://github.com/advisories/GHSA-3ww4-5jv9-j5gm
- github.com https://github.com/vllm-project/vllm/security/advisories/GHSA-3ww4-5jv9-j5gm