CVE-2026-54235: vLLM: temperature=NaN and temperature=Infinity bypass validation and propagate to GPU kernels

Published Jun 17, 2026
·
Updated

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

samplingparams.py:384: python if 0 < self.temperature < MAXTEMP: # NaN → False; +Inf → False

samplingparams.py:462: python if self.temperature < 0.0: # NaN → False; +Inf → False raise VLLMValidationError(...)

No math.isnan() or math.isinf() check exists anywhere in samplingparams.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 verifyargs(). 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

Other sources

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.

MITRE

Affected Software

2 affected components
pip/vllm<=0.23.0
vllm vllm<0.23.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/vllm to a version that resolves this vulnerability.

    Fixed in 0.23.1rc0
  2. Configuration

    Add math.isfinite(self.temperature) check in _verify_args() in sampling_params.py and raise VLLMValidationError (resulting in HTTP 400) for non-finite temperature values (NaN or +Infinity) so they are rejected before reaching GPU kernels.

    vllm (sampling_params.py) temperature validation in _verify_args() = math.isfinite(self.temperature) == True

Event History

Jun 17, 2026
Advisory Published
via GitHub·02:02 PM
Data Sourced
via GitHub·02:02 PM
DescriptionWeaknessAffected Software
Jun 22, 2026
CVE Published
via MITRE·09:59 PM
Data Sourced
via MITRE·09:59 PM
DescriptionWeakness
Data Sourced
via NVD·11:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-54235?

CVE-2026-54235 has a medium severity rating of 6.9.

2

How does CVE-2026-54235 affect software performance?

CVE-2026-54235 allows bypassing validation checks, which can lead to undefined behavior in GPU kernels.

3

What causes the vulnerability in CVE-2026-54235?

CVE-2026-54235 is caused by temperature validation gates using comparison operators that do not handle NaN and positive Infinity correctly.

4

Are there any known exploits for CVE-2026-54235?

As of now, there are no known public exploits specifically targeting CVE-2026-54235.

5

How can I mitigate CVE-2026-54235 in my application?

To mitigate CVE-2026-54235, ensure proper validation checks are implemented to handle NaN and Infinity values in temperature inputs.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203