Improper Validation of Array Index Affecting vllm-cu130 package, versions <0.29.0-r0


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.31% (23rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-VLLMCU130-20370473
  • published2 Oct 2026
  • disclosed26 Sept 2026

Introduced: 26 Sep 2026

NewCVE-2026-100654  (opens in a new tab)
CWE-129  (opens in a new tab)

How to fix?

Upgrade Minimos:latest vllm-cu130 to version 0.29.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream vllm-cu130 package and not the vllm-cu130 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

vLLM before 0.29.0 accepts user-controlled stop_token_ids on the OpenAI-compatible POST /v1/completions and POST /v1/chat/completions endpoints but validates only that the values are integers, not that each token id is within the model vocabulary/logits range. When min_tokens > 0, the stop token ids are used as logits indices to suppress stop tokens, so an out-of-range id reaches a CUDA indexing operation (index_put_) and triggers a device-side assertion. An authenticated API user can send a single malformed completion request that returns 500 Internal Server Error and puts EngineCore into a fatal state, causing subsequent requests to fail until the service is restarted (denial of service).

CVSS Base Scores

version 3.1