vllm
Affected
- introduced
0.8.5, fixed0.24.0(ecosystem)
Fixed versions
0.24.0
Fix
- Fixed version
0.24.0pip install --upgrade vllm==0.24.0
Advisory
Also known as: CVE-2026-54235, PYSEC-2026-3405
vLLM: temperature=NaN and temperature=Infinity bypass validation and propagate to GPU kernels
Summary
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.
Impact
Crash of inference worker on GPU kernel execution with NaN/Inf softmax input, degrading service for all concurrent users.
Remediation
Add math.isfinite(self.temperature) check in _verify_args(). Reject non-finite float values with a 400 error.
Fix
A fix for this vulnerability was merged here: https://github.com/vllm-project/vllm/pull/45116
Medium Basis: The source's own band: MODERATE
0.8.5, fixed 0.24.0 (ecosystem)0.24.0
0.24.0pip install --upgrade vllm==0.24.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0