VLLM (>= 0.17.1, < 0.24.0)

A frontend-legal multi-request speculative workload can cause vLLM to produce an out-of-vocabulary recovered token, which is then converted to an invalid value (-1) and reinjected into the drafting input IDs, leading to a GPU device-side assert and crashing the vLLM engine, causing a service-wide denial of service through a specific gRPC request sequence.