CVE-2026-47155

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

June 10, 2026

Last Modified

June 24, 2026

Advisory Details (4)

Auto-updated Jun 23, 2026
Patch available. Sources: github, github_pr, github_commit.
generic

huntr - The world's first bug bounty platform for AI/ML

https://huntr.com/bounties/3f1e24c0-87d2-4f6c-a705-820f380879ac
github_commit

commit d26a28ab0336 (vllm-project/vllm)

Fix landed in vllm-project/vllm commit d26a28ab0336 — awaiting tagged release

https://github.com/vllm-project/vllm/commit/d26a28ab033697f55a1414b5b0435de7cd6045b6
github_pr

fix: 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/42616
github Patch Available

Artifact 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-j5gm

Vendor Advisories for CVE-2026-47155(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhelai3/disk-image-cuda-rhel9:17882903142026-09-01redhat
redhatrhelai3/bootc-rocm-rhel9:17882606202026-09-01redhat
redhatrhaiis/vllm-spyre-rhel9:17871617762026-08-26redhat
redhatrhaiis/vllm-cuda-rhel9:17871613822026-08-24redhat
redhatrhaiis/vllm-rocm-rhel9:17871618032026-08-24redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
vllm0.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 7× in last 7d / 31× 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.

Showing the most recent 100 of 112 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-16 14:08 UTCEPSS rescore
  3. 2026-09-16 05:15 UTCEPSS rescore
  4. 2026-09-14 04:15 UTCEG score recompute
  5. 2026-09-14 04:15 UTCVendor advisory
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-08-31 00:12 UTCEG score recompute
  18. 2026-08-31 00:12 UTCVendor advisory
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-25 00:21 UTCEG score recompute
Show 75 more
  1. 2026-08-23 10:47 UTCEG score recompute
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-21 18:00 UTCEG score recompute
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 17:17 UTCEG score recompute
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 14:56 UTCEG score recompute
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-16 23:38 UTCEG score recompute
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 23:58 UTCEG score recompute
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-12 18:24 UTCEG score recompute
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-11 19:11 UTCEG score recompute
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-09 16:40 UTCEG score recompute
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-08 17:31 UTCEG score recompute
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-07 18:21 UTCEG score recompute
  25. 2026-08-06 19:11 UTCEG score recompute
  26. 2026-08-06 13:47 UTCEPSS rescore
  27. 2026-08-05 20:01 UTCEG score recompute
  28. 2026-08-05 19:17 UTCEPSS rescore
  29. 2026-08-04 15:54 UTCEG score recompute
  30. 2026-08-04 15:10 UTCEPSS rescore
  31. 2026-08-04 10:39 UTCEPSS rescore
  32. 2026-08-03 14:51 UTCEG score recompute
  33. 2026-08-03 10:36 UTCEPSS rescore
  34. 2026-08-02 08:51 UTCEG score recompute
  35. 2026-08-02 02:27 UTCEPSS rescore
  36. 2026-08-01 09:41 UTCEG score recompute
  37. 2026-08-01 04:16 UTCEPSS rescore
  38. 2026-07-31 09:11 UTCEG score recompute
  39. 2026-07-30 16:28 UTCEPSS rescore
  40. 2026-07-30 09:48 UTCEG score recompute
  41. 2026-07-30 01:30 UTCEPSS rescore
  42. 2026-07-29 04:57 UTCEG score recompute
  43. 2026-07-28 15:37 UTCEPSS rescore
  44. 2026-07-28 02:18 UTCEG score recompute
  45. 2026-07-27 14:13 UTCEPSS rescore
  46. 2026-07-26 21:00 UTCEG score recompute
  47. 2026-07-26 14:54 UTCEPSS rescore
  48. 2026-07-26 14:54 UTCEPSS rescore
  49. 2026-07-25 14:18 UTCEPSS rescore
  50. 2026-07-24 14:17 UTCEPSS rescore
  51. 2026-07-23 14:18 UTCEPSS rescore
  52. 2026-07-23 03:17 UTCEG score recompute
  53. 2026-07-22 14:08 UTCEPSS rescore
  54. 2026-07-21 15:24 UTCEPSS rescore
  55. 2026-07-20 17:08 UTCEPSS rescore
  56. 2026-07-19 14:31 UTCEPSS rescore
  57. 2026-07-19 02:29 UTCEPSS rescore
  58. 2026-07-18 10:04 UTCEPSS rescore
  59. 2026-07-16 17:03 UTCEPSS rescore
  60. 2026-07-15 16:57 UTCEPSS rescore
  61. 2026-07-15 02:00 UTCEPSS rescore
  62. 2026-07-13 22:30 UTCEPSS rescore
  63. 2026-07-13 06:13 UTCEPSS rescore
  64. 2026-07-12 05:46 UTCEPSS rescore
  65. 2026-07-11 08:27 UTCEPSS rescore
  66. 2026-07-09 19:10 UTCEPSS rescore
  67. 2026-07-08 15:16 UTCEPSS rescore
  68. 2026-07-07 13:46 UTCEPSS rescore
  69. 2026-07-06 02:23 UTCEPSS rescore
  70. 2026-07-05 02:30 UTCEPSS rescore
  71. 2026-07-04 06:31 UTCEPSS rescore
  72. 2026-07-01 15:07 UTCEPSS rescore
  73. 2026-06-30 23:22 UTCEPSS rescore
  74. 2026-06-29 14:06 UTCEPSS rescore
  75. 2026-06-29 14:06 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-47155?
CVE-2026-47155 is a medium vulnerability published on June 10, 2026. 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…
When was CVE-2026-47155 disclosed?
CVE-2026-47155 was first published in the National Vulnerability Database on June 10, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47155 actively exploited?
CVE-2026-47155 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.4% of all scored CVEs.
What is the CVSS score of CVE-2026-47155?
CVE-2026-47155 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-47155?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47155, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47155

Explore →

Is Your Infrastructure Affected by CVE-2026-47155?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs