INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2025-59425

vLLM is vulnerable to timing attack at bearer auth

CVE-2025-59425 ยท 2025-10-07 high

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Authentication and access control
Affected
vllm (PyPI)
Gets past
Authentication check
CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.6% chance of exploitation in 30 days

How it works, in short

The API key is checked with a non-constant-time string comparison, so response timing reveals correct characters and the key can be recovered incrementally. (Our summary, written by a model. The source text is below.)

Details

Summary

The API key support in vLLM performed validation using a method that was vulnerable to a timing attack. This could potentially allow an attacker to discover a valid API key using an approach more efficient than brute force.

Details

https://github.com/vllm-project/vllm/blob/4b946d693e0af15740e9ca9c0e059d5f333b1083/vllm/entrypoints/openai/api_server.py#L1270-L1274

API key validation used a string comparison that will take longer the more characters the provided API key gets correct. Data analysis across many attempts can allow an attacker to determine when it finds the next correct character in the key sequence.

### Impact
Deployments relying on vLLM's built-in API key validation are vulnerable to authentication bypass using this technique.

References

Source: GitHub Advisory Database, used under CC BY 4.0.