Skip to content
High-Impact Denial of Service Vulnerability in vLLM Project

High-Impact Denial of Service Vulnerability in vLLM Project

First seen 25 Oct 2026, 18:12 UTC • •
API

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 25, 2026 at 19:12 UTC
  • •CVE-2026-116180 affects vLLM versions 0.8.5 to 0.31.0, posing a high availability risk.
  • •The flaw allows low-privilege clients to crash the EngineCore, impacting co-tenant services.
  • •Immediate action is required: upgrade to fixed versions or restrict certain API functionalities.

A denial of service vulnerability (CVE-2026-116180) has been identified in vLLM versions 0.8.5 to 0.31.0. The flaw arises from the LogprobsTensors.empty_cpu() function, which allocates an uninitialized int32 tensor, causing the EngineCore to crash when specific API requests are made. This affects multi-tenant GPU inference platforms and hosted model APIs, allowing low-privilege clients to disrupt services for other users. The vulnerability is classified as high severity with a CVSS score of 8.3. Users are urged to upgrade to fixed versions or restrict the use of certain API features until a patch is applied. The risk is particularly high for services that are internet-reachable. The vulnerability was disclosed on October 25, 2026.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-25
CVE-2026-116180 published
A denial of service vulnerability in vLLM was disclosed, affecting versions 0.8.5 to 0.31.0.
Redpacketsecurity
2026-10-25
GitHub advisory released
GitHub published an advisory detailing the same vulnerability and its potential impact.
github.com

More articles in this cluster (2)

Following this threat?

Track CVE-2026-116180 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Extracted Entities (2)

1 / 2

Common questions

What versions are affected by CVE-2026-116180?
The vulnerability affects vLLM versions from 0.8.5 to 0.31.0.
What should I do if I'm using an affected version?
Upgrade to the fixed release or restrict the use of prompt_logprobs and echo options until patched.
How severe is this vulnerability?
It is classified as high severity with a CVSS score of 8.3, indicating a significant risk to availability.