Summary
vLLM: temperature=NaN and temperature=Infinity bypass validation and propagate to GPU kernels
All 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. Note: -Infinity is correctly caught.
Root Cause
sampling_params.py:384:
if 0 < self.temperature < _MAX_TEMP: # NaN → False; +Inf → False
sampling_params.py:462:
if self.temperature < 0.0: # NaN → False; +Inf → False
raise VLLMValidationError(...)
No math.isnan() or math.isinf() check exists anywhere in sampling_params.py.
Python semantics (verified): float('nan') < 0.0 → False, float('inf') < 0.0 → False.
Fix
A fix for this vulnerability was merged here: https://github.com/vllm-project/vllm/pull/45116
Impact
Crash of inference worker on GPU kernel execution with NaN/Inf softmax input, degrading service for all concurrent users.
CVE-2026-54235 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.24.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Add math.isfinite(self.temperature) check in _verify_args(). Reject non-finite float values with a 400 error.
Frequently Asked Questions
- What is CVE-2026-54235? CVE-2026-54235 is a medium-severity security vulnerability in vllm (pip), affecting versions >= 0.8.5, <= 0.23.0. It is fixed in 0.24.0.
- How severe is CVE-2026-54235? CVE-2026-54235 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of vllm are affected by CVE-2026-54235? vllm (pip) versions >= 0.8.5, <= 0.23.0 is affected.
- Is there a fix for CVE-2026-54235? Yes. CVE-2026-54235 is fixed in 0.24.0. Upgrade to this version or later.
- Is CVE-2026-54235 exploitable, and should I be worried? Whether CVE-2026-54235 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-54235 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-54235? Upgrade
vllmto 0.24.0 or later.