CVE-2026-54235·Python vulnerability
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.
- Severity
- medium
- Software
- Python
- Fixed in
- 0.23.1
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.26% — higher than 18% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
Until: 0.23.1
Fixed in: 0.23.1
How to fix this CVE
Update vLLM to version 0.23.1 or later to resolve temperature validation issues that can cause GPU sampling kernel crashes. The vulnerability allows invalid floating-point values (NaN and positive Infinity) to bypass validation checks and reach CUDA kernels, potentially causing worker process failures. Ensure your Python environment has the patched vLLM version installed before resuming LLM inference workloads.
sudo dnf update python3 && pip install --upgrade vllm>=0.23.1Defensia detects this vulnerability
How to check if you are affected
- Check installed vLLM version: python3 -c "import vllm; print(vllm.__version__)"
- Identify if vLLM is actively serving inference requests: ps aux | grep vllm
- Search inference worker logs for CUDA errors or crashes: grep -i "cuda\|segfault\|undefined behavior" /var/log/vllm/*.log
- Verify the fix by confirming version is >= 0.23.1: pip show vllm | grep Version
FAQ
What is CVE-2026-54235?
CVE-2026-54235 is a vulnerability in vLLM's temperature parameter validation that fails to reject NaN and positive Infinity values, allowing them to propagate to GPU sampling kernels and cause crashes or undefined behavior.
Is CVE-2026-54235 being actively exploited?
No, there is no evidence of active exploitation in the wild, and no public exploit code is available. However, the vulnerability can be triggered by malformed API requests, so defense-in-depth measures are recommended.
What versions of Python are affected by CVE-2026-54235?
vLLM versions prior to 0.23.1 are affected. The vulnerability exists in all releases up to and including 0.23.0, regardless of the underlying Python version.
How do I check if my server is vulnerable to CVE-2026-54235?
Run 'python3 -c "import vllm; print(vllm.__version__)"' and verify the version is 0.23.1 or later. If version is 0.23.0 or earlier, your deployment is vulnerable.
Does Defensia detect CVE-2026-54235?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If vLLM is installed on a monitored server, CVE-2026-54235 will appear in your dashboard with remediation steps.
Related Python CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-54235. Free for 1 server.
Get started free