vLLM - sampling parameter validation: Temperature validation uses strict comparison operators, so boundary values slip

Impact

Temperature validation uses strict comparison operators, so boundary values slip through the gate silently. In a multi-tenant serving deployment this is a request-parameter validation gap rather than memory corruption, but it lets a caller push the engine into a sampling state the operator believed was fenced off - which matters where sampling parameters are part of a tenant-facing safety or cost control.

Who can reach it

Network. Any client able to submit a request with sampling parameters to the vLLM endpoint.

What to do

Upgrade to vLLM 0.23.1rc0 or later and roll the serving deployment. Cost: rolling restart of the inference tier; no driver or firmware change.

References