CVE-2026-54235

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 82% 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, nvd
Trending — 4 sources updated this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

A fix is available — apply it.

vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.23.1rc0, ll temperature validation gates use comparison operators (<, >), which silently evaluate to False for NaN and for positive Infinity in Python's IEEE 754 float semantics. Both values pass every guard and propagate to GPU sampling kernels, where they produce undefined behavior or CUDA errors that can crash the inference worker. This vulnerability is fixed in 0.23.1rc0.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
44(Track)
EG Risk 44/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%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
17.8%
KEV
Not listed

Published

June 17, 2026

Last Modified

June 24, 2026

Advisory Details (3)

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

temperature=NaN and temperature=Infinity bypass validation and propagate to GPU kernels · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-7h4p-rffg-7823
github_pr

[Security] Reject non-finite temperature and repetition_penalty values

Fix merged in vllm-project/vllm PR #45116 on 2026-06-11 — awaiting tagged release

https://github.com/vllm-project/vllm/pull/45116
github_commit

commit d598d239737c (vllm-project/vllm)

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

https://github.com/vllm-project/vllm/commit/d598d239737cfa37bcfcb98886ec3f3557fc7198

Vendor Advisories for CVE-2026-54235(3)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhaiis/vllm-rocm-rhel9:17829512442026-07-06redhat
redhatrhaiis/vllm-cuda-rhel9:17829510122026-07-06redhat
pipvllm—ghsa

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 (89 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 77× 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-23 03:19 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 21:47 UTCVendor advisory
  10. 2026-07-16 21:47 UTCGHSA enrichment
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 13:17 UTCVendor advisory
  15. 2026-07-15 13:17 UTCGHSA enrichment
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-14 10:07 UTCVendor advisory
  19. 2026-07-14 10:07 UTCGHSA enrichment
  20. 2026-07-13 22:31 UTCEPSS rescore
  21. 2026-07-13 07:56 UTCVendor advisory
  22. 2026-07-13 07:56 UTCGHSA enrichment
  23. 2026-07-13 06:13 UTCEPSS rescore
  24. 2026-07-13 06:13 UTCEPSS rescore
  25. 2026-07-12 05:50 UTCVendor advisory
Show 58 more
  1. 2026-07-12 05:50 UTCGHSA enrichment
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-11 03:45 UTCVendor advisory
  6. 2026-07-11 03:45 UTCGHSA enrichment
  7. 2026-07-10 01:40 UTCVendor advisory
  8. 2026-07-10 01:40 UTCGHSA enrichment
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-08 22:14 UTCVendor advisory
  12. 2026-07-08 22:14 UTCGHSA enrichment
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-07 20:10 UTCVendor advisory
  16. 2026-07-07 20:10 UTCGHSA enrichment
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 12:26 UTCGHSA enrichment
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-05 06:29 UTCGHSA enrichment
  25. 2026-07-05 02:31 UTCEPSS rescore
  26. 2026-07-05 02:30 UTCEPSS rescore
  27. 2026-07-04 06:31 UTCEPSS rescore
  28. 2026-07-04 06:31 UTCEPSS rescore
  29. 2026-07-04 03:31 UTCGHSA enrichment
  30. 2026-07-03 00:34 UTCGHSA enrichment
  31. 2026-07-01 22:26 UTCGHSA enrichment
  32. 2026-07-01 15:07 UTCEPSS rescore
  33. 2026-06-30 23:22 UTCEPSS rescore
  34. 2026-06-30 19:56 UTCGHSA enrichment
  35. 2026-06-29 17:50 UTCGHSA enrichment
  36. 2026-06-29 14:06 UTCEPSS rescore
  37. 2026-06-29 14:06 UTCEPSS rescore
  38. 2026-06-28 15:44 UTCGHSA enrichment
  39. 2026-06-28 14:07 UTCEPSS rescore
  40. 2026-06-28 04:56 UTCEPSS rescore
  41. 2026-06-28 04:56 UTCEPSS rescore
  42. 2026-06-27 13:38 UTCGHSA enrichment
  43. 2026-06-27 03:08 UTCEPSS rescore
  44. 2026-06-26 11:33 UTCGHSA enrichment
  45. 2026-06-25 13:49 UTCEPSS rescore
  46. 2026-06-25 04:18 UTCEG score recompute▼ 0.40
  47. 2026-06-25 04:18 UTCGHSA enrichment
  48. 2026-06-24 18:02 UTCNVD updateCVSS v3 → 6.5
  49. 2026-06-24 14:05 UTCEPSS rescore
  50. 2026-06-24 02:09 UTCGHSA enrichment
  51. 2026-06-23 21:33 UTCEPSS rescore
  52. 2026-06-23 21:33 UTCEPSS rescore
  53. 2026-06-23 00:04 UTCEG score recompute▲ 6.90
  54. 2026-06-23 00:03 UTCGHSA enrichment
  55. 2026-06-23 00:00 UTCMITRE cvelistV5CVSS v3 → 6.9 · CVSS v4 → 6.9
  56. 2026-06-20 13:26 UTCGHSA enrichment
  57. 2026-06-17 14:06 UTCEG score recompute
  58. 2026-06-17 14:06 UTCGHSA enrichment

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-54235?
CVE-2026-54235 is a medium vulnerability published on June 17, 2026. vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.23.1rc0, ll temperature validation gates use comparison operators (<, >), which silently evaluate to False for NaN and for positive Infinity in Python's IEEE 754 float semantics. Both values pass every guard and…
When was CVE-2026-54235 disclosed?
CVE-2026-54235 was first published in the National Vulnerability Database on June 17, 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-54235 actively exploited?
CVE-2026-54235 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54235?
CVE-2026-54235 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-54235?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54235, 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-54235

Explore →

Is Your Infrastructure Affected by CVE-2026-54235?

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

Start Free Scan →Browse All CVEs