VDB
CVE-2026-93989
CVE-2026-93989
PUBLISHED
CVSS 2.3 LOW
vLLM through 0.29.0 Cross-Request Logits Corruption via bad_words
Reported by vulncheck · Published September 19, 2026
vLLM through 0.29.0 fails to properly validate bad_words token indices against the model's generation output width in SamplingParams.update_from_tokenizer(). Attackers can supply out-of-bounds token indices that corrupt logits memory of concurrent requests, causing different in-flight HTTP requests to return incorrect tokens.
Risk scores
CVSS 4.0
2.3
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Affected products
| Vendor | Product | Versions |
|---|---|---|
| vllm-project | vllm | 0 |
| vllm | vllm | 0 |
| vllm-project | vllm | 0 |
Timeline
- Sep 19, 2026 CVE Published
- Sep 20, 2026 EPSS Score (12 in total, the first dated here)
- Sep 20, 2026 Coalition ESS Score
- Sep 22, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-93989
vulnetix vdb fixes CVE-2026-93989
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-93989/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- GitHub PR #48824 issue-trackingpatch
- _bad_words_kernel at v0.29.0 technical-description
- update_from_tokenizer at v0.29.0 technical-description
- product
- VulnCheck Advisory: vLLM through 0.29.0 Cross-Request Logits Corruption via bad_words third-party-advisory