vLLM from 0.9.2 before 0.24.0 contains a server-side request forgery vulnerability that allows API callers to force outbound connections by embedding

Summary

vLLM from 0.9.2 before 0.24.0 contains a server-side request forgery vulnerability that allows API callers to force outbound connections by embedding a decode address in the X-Request-Id header. Attackers can make a P2pNcclConnector prefill worker ZMQ-connect to an attacker host, leaking the NCCL unique_id and KV-cache tensors or blocking the worker.

Remediation

1. Inventory every Vllm Vllm deployment, including staging.
2. Upgrade Vllm Vllm to 0.24.0.
3. Confirm the running version after the upgrade.

References

• Advisoryhttps://github.com/vllm-project/vllm/security/advisories/GHSA-vfp2-c8pq-v6h6
• Advisoryhttps://www.vulncheck.com/advisories/vllm-0.9.2-before-0.24.0-ssrf-via-x-request-id-in-p2pncclconnector