CWE
502
Advisory Published
Updated

GHSA-9pcc-gvx5-r5wm

First published: Tue May 06 2025(Updated: )

### Affected Environments Note that this issue only affects the V0 engine, which has been off by default since v0.8.0. Further, the issue only applies to a deployment using tensor parallelism across multiple hosts, which we do not expect to be a common deployment pattern. Since V0 is has been off by default since v0.8.0 and the fix is fairly invasive, we have decided not to fix this issue. Instead we recommend that users ensure their environment is on a secure network in case this pattern is in use. The V1 engine is not affected by this issue. ### Impact In a multi-node vLLM deployment using the V0 engine, vLLM uses ZeroMQ for some multi-node communication purposes. The secondary vLLM hosts open a `SUB` ZeroMQ socket and connect to an `XPUB` socket on the primary vLLM host. https://github.com/vllm-project/vllm/blob/c21b99b91241409c2fdf9f3f8c542e8748b317be/vllm/distributed/device_communicators/shm_broadcast.py#L295-L301 When data is received on this `SUB` socket, it is deserialized with `pickle`. This is unsafe, as it can be abused to execute code on a remote machine. https://github.com/vllm-project/vllm/blob/c21b99b91241409c2fdf9f3f8c542e8748b317be/vllm/distributed/device_communicators/shm_broadcast.py#L468-L470 Since the vulnerability exists in a client that connects to the primary vLLM host, this vulnerability serves as an escalation point. If the primary vLLM host is compromised, this vulnerability could be used to compromise the rest of the hosts in the vLLM deployment. Attackers could also use other means to exploit the vulnerability without requiring access to the primary vLLM host. One example would be the use of ARP cache poisoning to redirect traffic to a malicious endpoint used to deliver a payload with arbitrary code to execute on the target machine.

Affected SoftwareAffected VersionHow to fix
pip/vllm>=0.5.2<=0.8.5.post1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of GHSA-9pcc-gvx5-r5wm?

    The severity of GHSA-9pcc-gvx5-r5wm is low as it only affects the V0 engine which is off by default.

  • How do I fix GHSA-9pcc-gvx5-r5wm?

    To mitigate GHSA-9pcc-gvx5-r5wm, upgrade vllm to a version greater than 0.8.5.post1.

  • Which versions of vllm are affected by GHSA-9pcc-gvx5-r5wm?

    GHSA-9pcc-gvx5-r5wm affects vllm versions from 0.5.2 to 0.8.5.post1 inclusive.

  • What environments are affected by GHSA-9pcc-gvx5-r5wm?

    GHSA-9pcc-gvx5-r5wm affects environments using the V0 engine with tensor parallelism across multiple hosts.

  • Is GHSA-9pcc-gvx5-r5wm common?

    The issue described in GHSA-9pcc-gvx5-r5wm is expected to be rare due to the uncommon deployment pattern it affects.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203