# vLLM's Artifact Pin Decay allows pinned deployments to load unpinned code, weights, and processors

Advisory record · `GHSA-3ww4-5jv9-j5gm`

- **Identifiers:** `GHSA-3ww4-5jv9-j5gm` · `CVE-2026-47155` · `PYSEC-2026-2301`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-345](https://cwe.mitre.org/data/definitions/345.html)
- **Tags:** [CWE-345](https://agentprime.io/advisories/tag/cwe-345.md)
- **Published:** 10 Jun 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Jun 2026, 17:11 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `vllm` (PyPI): affected `<0.22.0`; fixed in `0.22.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> vLLM versions before 0.22.0 do not apply revision pins consistently to all artifacts loaded for a model, so a deployment that sets a model or code revision can still load dynamic code, GGUF files, image processors, or side weights from an unpinned default revision. The source describes this as an integrity issue rather than a remote code execution flaw, and the attacker would need to change those artifacts in the upstream repository. Upgrade vLLM to 0.22.0 or later, which the source lists as the fixed version.

Written 4 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0025, the 16th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:29 UTC: First seen by agentprime
- 31 Oct 2026, 14:29 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3ww4-5jv9-j5gm)

## Sources

- [GitHub Advisory Database: GHSA-3ww4-5jv9-j5gm](https://github.com/advisories/GHSA-3ww4-5jv9-j5gm)
- [OSV: GHSA-3ww4-5jv9-j5gm](https://osv.dev/vulnerability/GHSA-3ww4-5jv9-j5gm)
- <https://github.com/vllm-project/vllm/security/advisories/GHSA-3ww4-5jv9-j5gm>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-47155>
- <https://github.com/vllm-project/vllm/pull/42616>
- <https://github.com/vllm-project/vllm/commit/d26a28ab033697f55a1414b5b0435de7cd6045b6>
- <https://github.com/pypa/advisory-database/tree/main/vulns/vllm/PYSEC-2026-2301.yaml>
- <https://github.com/vllm-project/vllm>
- <https://huntr.com/bounties/3f1e24c0-87d2-4f6c-a705-820f380879ac>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-3ww4-5jv9-j5gm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3ww4-5jv9-j5gm/>. Everything for agents: <https://agentprime.io/llms.txt>.