Quick answers
- Is CVE-2026-114051 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114051 being exploited in the wild.
- How severe is CVE-2026-114051?
- High severity, with a CVSS score of 7.5, published 21 October 2026.
- Which products and versions are affected?
- vLLM Project vllm before 0.31.0.
- Is there a fix for CVE-2026-114051?
- Yes: fixed in 0.31.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114051 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-114051?
- Check whether you run vLLM Project vllm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.31.0
Technical details
The vulnerability stems from a skipped min_tokens ≤ max_tokens validation check when max_tokens is null in /inference/v1/generate requests. The API process creates SamplingParams without validation, the EngineCore later rebuilds the params, validation fails with an uncaught VLLMValidationError on the decode line, and the exception is not caught by the surrounding try-except, killing the input thread. This is a denial-of-service via improper exception handling (CWE-248, CWE-754) requiring only network access.
Affected products
- vLLM Project vLLM before 0.31.0
Timeline
- 2026-10-06: disclosed
- 2026-10-20: advisory
- 2026-10-21: patched