Live › vulnerability › CVE-2026-116172
Go to dashboardvLLM versions 0.22.0 before 0.24.0 fail to validate the top_n field in the Rust gRPC converter, so the max_logprobs limit can be bypassed. A remote attacker sending Generate or GenerateStream requests with oversized or integer-wrapping top_n values makes torch.topk fail and terminates EngineCore, which takes the model server down.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-25 14:41 UTC. All times on this page are UTC.
Teams that run vLLM 0.22.0 through 0.24.0 with the Rust gRPC frontend serving Generate or GenerateStream requests. Exposure is greatest where the gRPC port is reachable from untrusted clients. Teams on earlier or later versions, or using only the HTTP API, can likely skip it, but the sources do not say which API surface is affected.
No product ranges from the sources yet.
pip show vllm and confirm whether the version is at least 0.22.0 and below 0.24.0.0.24.0 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
vLLM from 0.22.0 before 0.24.0 contains an improper input validation vulnerability in the Rust gRPC converter that allows remote attackers to bypass max_logprobs limits via CandidateTokens.top_n. Attackers can send Generate or GenerateStream requests with oversized or integer-wrapping top_n values to trigger torch.topk failures that terminate EngineCore.
This page as .md · .json · in your agent: get_signal("CVE-2026-116172")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.