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 81% 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 — 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.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 PROB
0%
EPSS %ILE
19%
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)0.24.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 69× 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 150 total refreshes for this CVE.

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

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 0% probability of exploitation in the next 30 days, which ranks it in the top 80.6% of all scored CVEs.
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