CVE-2026-93841
Reported by vulncheck · Published September 18, 2026
vLLM through 0.29.0 contains a memory corruption vulnerability in the Triton _bincount_kernel where prompt token IDs index the penalty prompt-presence bitset without bounds checking against vocabulary size. Attackers can submit multimodal audio requests with tokens equal to vocabulary size, causing out-of-bounds writes that corrupt concurrent requests' sampler state and alter repetition penalty behavior.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| vllm | vllm | 0.29.0 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| vllm-project | vllm | 0 |
| vllm | vllm | 0 |
| vllm-project | vllm | 0 |
Timeline
- Sep 18, 2026 CVE Published
- Sep 19, 2026 EPSS Score (14 in total, the first dated here)
- Sep 28, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-93841
vulnetix vdb fixes CVE-2026-93841
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-93841/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- patchissue-tracking
- product
- technical-description
- technical-description
- VulnCheck Advisory: vLLM through 0.29.0 Adjacent-Request Sampler State Corruption via Unvalidated Prompt Token IDs third-party-advisory