CVE-2026-54232

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% 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
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.22.1, the vLLM Dockerfile is vulnerable to a dependency confusion attack through the flashinfer-jit-cache package. The package is installed from a custom index (flashinfer.ai/whl/) using --extra-index-url, but the package name was not registered on PyPI, and UV_INDEX_STRATEGY="unsafe-best-match" is set globally. An attacker who registers flashinfer-jit-cache on PyPI with version 0.6.11.post2 can execute arbitrary code as root during the Docker build and backdoor every resulting container image, enabling exfiltration of all user prompts, API credentials, and model data from production vLLM deployments This vulnerability is fixed in 0.22.1.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
22.3%
KEV
Not listed

Published

June 22, 2026

Last Modified

June 24, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Dependency Confusion Vulnerability in vLLM Dockerfile · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-jrf6-vqxq-pjv2

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
vllm0.0.1 ... 0.9.2 (87 versions)0.22.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 70× 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.

  1. 2026-07-12 05:56 UTCEG score recompute
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-11 18:12 UTCEG score recompute
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-11 06:28 UTCEG score recompute
  7. 2026-07-10 18:30 UTCEG score recompute
  8. 2026-07-10 06:23 UTCEG score recompute
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-09 18:38 UTCEG score recompute
  12. 2026-07-09 06:54 UTCEG score recompute
  13. 2026-07-08 19:07 UTCEG score recompute
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-08 15:16 UTCEPSS rescore
  16. 2026-07-08 07:23 UTCEG score recompute
  17. 2026-07-07 19:39 UTCEG score recompute
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-07 13:46 UTCEPSS rescore
  20. 2026-07-07 06:58 UTCEG score recompute
  21. 2026-07-06 18:46 UTCEG score recompute
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-06 16:27 UTCEPSS rescore
  24. 2026-07-06 06:30 UTCEG score recompute
  25. 2026-07-06 02:23 UTCEPSS rescore
Show 45 more
  1. 2026-07-06 02:23 UTCEPSS rescore
  2. 2026-07-05 18:46 UTCEG score recompute
  3. 2026-07-05 07:01 UTCEG score recompute
  4. 2026-07-05 02:31 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 19:16 UTCEG score recompute
  7. 2026-07-04 07:31 UTCEG score recompute
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-03 19:14 UTCEG score recompute
  11. 2026-07-03 07:29 UTCEG score recompute
  12. 2026-07-02 19:45 UTCEG score recompute
  13. 2026-07-02 08:01 UTCEG score recompute
  14. 2026-07-01 20:16 UTCEG score recompute
  15. 2026-07-01 15:07 UTCEPSS rescore
  16. 2026-07-01 08:32 UTCEG score recompute
  17. 2026-06-30 23:22 UTCEPSS rescore
  18. 2026-06-30 20:48 UTCEG score recompute
  19. 2026-06-30 09:04 UTCEG score recompute
  20. 2026-06-29 21:19 UTCEG score recompute
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 09:35 UTCEG score recompute
  24. 2026-06-28 21:49 UTCEG score recompute
  25. 2026-06-28 14:07 UTCEPSS rescore
  26. 2026-06-28 10:05 UTCEG score recompute
  27. 2026-06-28 04:56 UTCEPSS rescore
  28. 2026-06-28 04:56 UTCEPSS rescore
  29. 2026-06-27 22:20 UTCEG score recompute
  30. 2026-06-27 10:36 UTCEG score recompute
  31. 2026-06-27 03:08 UTCEPSS rescore
  32. 2026-06-26 22:51 UTCEG score recompute
  33. 2026-06-26 11:07 UTCEG score recompute
  34. 2026-06-25 22:32 UTCEG score recompute
  35. 2026-06-25 13:49 UTCEPSS rescore
  36. 2026-06-25 10:48 UTCEG score recompute
  37. 2026-06-24 23:04 UTCEG score recompute
  38. 2026-06-24 14:05 UTCEPSS rescore
  39. 2026-06-24 11:20 UTCEG score recompute
  40. 2026-06-23 23:35 UTCEG score recompute
  41. 2026-06-23 21:33 UTCEPSS rescore
  42. 2026-06-23 21:33 UTCEPSS rescore
  43. 2026-06-23 11:49 UTCEG score recompute
  44. 2026-06-23 00:03 UTCEG score recompute
  45. 2026-06-23 00:00 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54232?
CVE-2026-54232 is a high vulnerability published on June 22, 2026. vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.22.1, the vLLM Dockerfile is vulnerable to a dependency confusion attack through the flashinfer-jit-cache package. The package is installed from a custom index (flashinfer.ai/whl/) using --extra-index-url, but the…
When was CVE-2026-54232 disclosed?
CVE-2026-54232 was first published in the National Vulnerability Database on June 22, 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-54232 actively exploited?
CVE-2026-54232 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54232?
CVE-2026-54232 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-54232?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54232, 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-54232

Explore →

Is Your Infrastructure Affected by CVE-2026-54232?

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

Start Free Scan →Browse All CVEs