6.5
MEDIUM CVSS 3.1
CVE-2026-47155
vLLM: Artifact Pin Decay in vLLM allows pinned deployments to load unpinned code, weights, and processors
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.

INFO

Published Date :

June 22, 2026, 11:16 p.m.

Last Modified :

June 24, 2026, 4:49 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-47155 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Vllm-project vllm
1 Vllm vllm
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 134c704f-9b21-4f2e-91b3-4a467353bcc0
CVSS 3.1 MEDIUM [email protected]
Solution
Update vLLM to version 0.22.0 or later to ensure revision pinning applies consistently.
  • Update vLLM to version 0.22.0 or later.
  • Verify artifact integrity after updating.
  • Ensure all model artifacts are consistently pinned.
Public PoC/Exploit Available at Github

CVE-2026-47155 has a 1 public PoC/Exploit available at Github. Go to the Public Exploits tab to see the list.

References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-47155.

URL Resource
https://github.com/vllm-project/vllm/commit/d26a28ab033697f55a1414b5b0435de7cd6045b6 Patch
https://github.com/vllm-project/vllm/pull/42616 Issue Tracking
https://github.com/vllm-project/vllm/security/advisories/GHSA-3ww4-5jv9-j5gm Third Party Advisory
https://huntr.com/bounties/3f1e24c0-87d2-4f6c-a705-820f380879ac Third Party Advisory
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-47155 is associated with the following CWEs:

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

None

Updated: 3 weeks ago
0 stars 0 fork 0 watcher
Born at : April 22, 2026, 7:41 a.m. This repo has been linked 3 different CVEs too.

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-47155 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-47155 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Initial Analysis by [email protected]

    Jun. 24, 2026

    Action Type Old Value New Value
    Added CPE Configuration OR *cpe:2.3:a:vllm:vllm:*:*:*:*:*:*:*:* versions up to (excluding) 0.22.0
    Added Reference Type GitHub, Inc.: https://github.com/vllm-project/vllm/commit/d26a28ab033697f55a1414b5b0435de7cd6045b6 Types: Patch
    Added Reference Type GitHub, Inc.: https://github.com/vllm-project/vllm/pull/42616 Types: Issue Tracking
    Added Reference Type GitHub, Inc.: https://github.com/vllm-project/vllm/security/advisories/GHSA-3ww4-5jv9-j5gm Types: Third Party Advisory
    Added Reference Type GitHub, Inc.: https://huntr.com/bounties/3f1e24c0-87d2-4f6c-a705-820f380879ac Types: Third Party Advisory
  • CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Jun. 23, 2026

    Action Type Old Value New Value
    Added SSVC {'id': 'CVE-2026-47155', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'partial'}], 'version': '2.0.3', 'timestamp': '2026-06-23T12:34:39.566846Z'}
  • New CVE Received by [email protected]

    Jun. 22, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'vllm-project', 'product': 'vllm', 'versions': [{'status': 'affected', 'version': '< 0.22.0'}]}]
    Added 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.
    Added CVSS V3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N
    Added CWE CWE-345
    Added Reference https://github.com/vllm-project/vllm/commit/d26a28ab033697f55a1414b5b0435de7cd6045b6
    Added Reference https://github.com/vllm-project/vllm/pull/42616
    Added Reference https://github.com/vllm-project/vllm/security/advisories/GHSA-3ww4-5jv9-j5gm
    Added Reference https://huntr.com/bounties/3f1e24c0-87d2-4f6c-a705-820f380879ac
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.