vLLM 0.11.0 Release Candidate 1
Approved changes feed: RSS · Atom
cpe:2.3:a:vllm:vllm:0.11.0:rc1:*:*:*:*:*:*part: a version: 0.11.0 update: rc1
| Vendor | Vllm (78d29c10-0b9d-5211-926e-f14f4fcee1c3) |
|---|---|
| Product | Vllm (89ccd1da-5f71-5221-b734-cddd65c3b44f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from NVD CPE 2.0 feed
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/vllm-project/vllm |
purl2cpe | 2026-06-01 10:11:52.853553 |
pkg:pypi/vllm |
purl2cpe | 2026-06-01 10:11:52.853555 |
pkg:sourceforge/vllm.mirror |
purl2cpe | 2026-06-01 10:11:52.853556 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-59425 |
vulnerable | 2026-06-08 07:35:21.893908 |
vLLM vulnerable to timing attack at bearer auth
HIGH (7.5)
vLLM is an inference and serving engine for large language models (LLMs). Before version 0.11.0rc2, the API key support in vLLM performs validation using a method that was vulnerable to a timing attack. API key validation uses a string comparison that takes longer the more characters the provided API key gets correct. Data analysis across many attempts could allow an attacker to determine when it finds the next correct character in the key sequence. Deployments relying on vLLM's built-in API key validation are vulnerable to authentication bypass using this technique. Version 0.11.0rc2 fixes the issue.
Published: 2025-10-07T14:06:49.042Z
Updated: 2025-10-07T15:28:10.303Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.