MediumVulnerabilityLLM-specific
CVE-2026-100652: vLLM stop_token_ids validation flaw in Rust HTTP and gRPC frontends
- Source
- NVD(opens in a new tab)
- Identifier
- CVE-2026-100652
- Published
- Record updated
- Known exploitation
- Not listed in the CISA Known Exploited Vulnerabilities catalog at the last check.
- EPSS
- 0.4%
Summary
vLLM versions 0.22.0 through 0.23.0 do not validate stop_token_ids against vocabulary bounds in the Rust HTTP and gRPC frontends, so out-of-vocabulary token IDs reach MinTokensLogitsProcessor. An attacker can send requests with min_tokens greater than zero and out-of-vocabulary stop_token_ids to trigger CUDA tensor indexing failures, which leave EngineCore in a fatal state that requires a service restart.
Mitigation
The source does not state a fix yet. Check the original advisory for updates.
Topics
Related items
- MediumEndor Labs’ AI SAST Finds Zero Day Memory-Amplification DoS in Anthropic’s buffa library | Endor LabsSimilar attack · Endor Labs Blog
- MediumCVE-2026-44627: Intel oneDNN integer overflow to buffer overflow in Ring 3 user applicationsSimilar attack · NVD/CVE Database
- MediumGHSA-h7c4-q426-7jh9: tsParticles: A single anonymous MCP session can monopolize HTTP mode and deny new clientsSimilar attack · GitHub Advisory Database
- HighGHSA-4p8p-pjpq-2w7h: tsParticles: Malformed JSON requests can terminate the @tsparticles/mcp-server HTTP processSimilar attack · GitHub Advisory Database
- HighGHSA-447x-qqwf-m7xq: tsParticles: Unbounded HTTP Request Body Buffering in @tsparticles/mcp-server Leads to Remote DoSSimilar attack · GitHub Advisory Database