Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of vLLM before 0.30.0 are affected, with confirmed reports on 0.25.1. Three structured-output request paths let a single ordinary request raise an uncaught exception that terminates the shared EngineCore, denying service to all other requests on that engine. The source gives few details on the exact trigger conditions for the third path. Upgrade to vLLM 0.30.0 or later.
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 |
|---|---|---|---|---|
| 6.5 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0031, the 24th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:08 UTC First seen by agentprime
- 31 Oct 2026, 14:08 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-85xf-c7hm-whqw
- OSV: GHSA-85xf-c7hm-whqw
- github.com/vllm-project/vllm/security/advisories/GHSA-85xf-c7hm-whqw
- github.com/vllm-project/vllm/pull/51450
- github.com/vllm-project/vllm/commit/c55e15a44ec4127832d4a86928a356fdd9e68dbd
- github.com/vllm-project/vllm
- github.com/vllm-project/vllm/releases/tag/v0.30.0