Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The vLLM package, versions before 0.26.0, has an issue in its /v1/completions/derender and /v1/chat/completions/derender endpoints, which accept caller-supplied generated token IDs without enforcing output size limits. An authenticated API client can make the server spend CPU and memory detokenizing oversized payloads, affecting availability for other clients. Upgrade to vLLM 0.26.0 or later, which contains the fix.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 4.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0037, the 31st percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:10 UTC First seen by agentprime
- 31 Oct 2026, 14:10 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-8737-qx52-hjff
- OSV: GHSA-8737-qx52-hjff
- github.com/vllm-project/vllm/security/advisories/GHSA-8737-qx52-hjff
- nvd.nist.gov/vuln/detail/CVE-2026-71486
- github.com/vllm-project/vllm/pull/47260
- github.com/vllm-project/vllm/commit/8e61b646e2d157f9b93451fa048f9c8530c8a67b
- github.com/vllm-project/vllm
- github.com/vllm-project/vllm/releases/tag/v0.26.0