{"id":"CVE-2024-9052","aliases":["EUVD-2025-6864","GHSA-pgr7-mhp5-fgjp","PYSEC-2026-568"],"status":"rejected","title":"vLLM deserialization vulnerability in vllm.distributed.GroupCoordinator.recv_object","description":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","severity":{"version":"3.0","score":9.8,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","from":"ghsa"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-502"],"published":"2025-03-20T10:09:31Z","modified":"2026-10-16T14:10:00Z","affected":[{"source":"ghsa","ecosystem":"PyPI","package":"vllm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.8.1"}]}]},{"source":"osv","ecosystem":"PyPI","package":"vllm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.8.1"}]}],"versions":["0.0.1","0.1.0","0.1.1","0.1.2","0.1.3","0.1.4","0.1.5","0.1.6","0.1.7","0.2.0","0.2.1","0.2.1.post1","0.2.2","0.2.3","0.2.4","0.2.5","0.2.6","0.2.7","0.3.0","0.3.1","0.3.2","0.3.3","0.4.0","0.4.0.post1","0.4.1","0.4.2","0.4.3","0.5.0","0.5.0.post1","0.5.1","0.5.2","0.5.3","0.5.3.post1","0.5.4","0.5.5","0.6.0","0.6.1","0.6.1.post1","0.6.1.post2","0.6.2","0.6.3","0.6.3.post1","0.6.4","0.6.4.post1","0.6.5","0.6.6","0.6.6.post1","0.7.0","0.7.1","0.7.2","0.7.3","0.8.0","0.8.1"]},{"source":"osv","ecosystem":"PyPI","package":"vllm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.8.1"}]}],"versions":["0.0.1","0.1.0","0.1.1","0.1.2","0.1.3","0.1.4","0.1.5","0.1.6","0.1.7","0.2.0","0.2.1","0.2.1.post1","0.2.2","0.2.3","0.2.4","0.2.5","0.2.6","0.2.7","0.3.0","0.3.1","0.3.2","0.3.3","0.4.0","0.4.0.post1","0.4.1","0.4.2","0.4.3","0.5.0","0.5.0.post1","0.5.1","0.5.2","0.5.3","0.5.3.post1","0.5.4","0.5.5","0.6.0","0.6.1","0.6.1.post1","0.6.1.post2","0.6.2","0.6.3","0.6.3.post1","0.6.4","0.6.4.post1","0.6.5","0.6.6","0.6.6.post1","0.7.0","0.7.1","0.7.2","0.7.3","0.8.0","0.8.1"]}],"products":[{"vendor":"vllm-project","product":"vllm-project/vllm"}],"references":[{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-9052","tags":["advisory"]},{"url":"https://huntr.com/bounties/ea75728f-4efe-4a3d-9f53-33f2c908e9f8","tags":["web"]},{"url":"https://github.com/vllm-project/vllm/blob/32e7db25365415841ebc7c4215851743fbb1bad1/vllm/distributed/parallel_state.py#L480","tags":["web"]},{"url":"https://github.com/vllm-project/vllm/blob/v0.8.1/vllm/distributed/parallel_state.py#L457","tags":["web"]},{"url":"https://github.com/github/advisory-database/pull/5444","tags":["web"]},{"url":"https://github.com/advisories/GHSA-pgr7-mhp5-fgjp","tags":["advisory"]},{"url":"https://github.com/vllm-project/vllm","tags":["package"]},{"url":"https://pypi.org/project/vllm","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2024-9052","description":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","status":"rejected","published":"2025-03-20T10:09:31.436Z","modified":"2025-04-10T16:17:38.776Z","updated_at":"2026-11-02T14:34:06.147811Z"}],"euvd":[{"id":"EUVD-2025-6864","description":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","status":"published","published":"2025-03-20T10:09:31Z","modified":"2025-04-10T16:17:38Z","cvss":[{"version":"3.0","score":9.8,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T20:52:36.312116Z"}],"ghsa":[{"id":"GHSA-pgr7-mhp5-fgjp","title":"vLLM deserialization vulnerability in vllm.distributed.GroupCoordinator.recv_object","description":"vllm-project vllm version 0.6.0 contains a vulnerability in the distributed training API. The function vllm.distributed.GroupCoordinator.recv_object() deserializes received object bytes using pickle.loads() without sanitization, leading to a remote code execution vulnerability.\n\n### Maintainer perspective\nNote that vLLM does NOT use the code as described in the report on huntr. The problem only exists if you use these internal APIs in a way that exposes them to a network as described. The vllm team was not involved in the analysis of this report and the decision to assign it a CVE.","status":"published","published":"2025-03-20T12:32:50Z","modified":"2025-04-09T17:02:39Z","cvss":[{"version":"3.0","score":9.8,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-502"],"updated_at":"2026-11-02T14:38:38.344711Z"}],"nvd":[{"id":"CVE-2024-9052","description":"Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","status":"rejected","published":"2025-03-20T10:15:46.197Z","modified":"2026-10-16T14:10:00.12Z","updated_at":"2026-11-02T14:10:45.815983Z"}],"osv":[{"id":"GHSA-pgr7-mhp5-fgjp","title":"vLLM deserialization vulnerability in vllm.distributed.GroupCoordinator.recv_object","description":"vllm-project vllm version 0.6.0 contains a vulnerability in the distributed training API. The function vllm.distributed.GroupCoordinator.recv_object() deserializes received object bytes using pickle.loads() without sanitization, leading to a remote code execution vulnerability.\n\n### Maintainer perspective\nNote that vLLM does NOT use the code as described in the report on huntr. The problem only exists if you use these internal APIs in a way that exposes them to a network as described. The vllm team was not involved in the analysis of this report and the decision to assign it a CVE.","status":"published","published":"2025-03-20T12:32:50Z","modified":"2026-08-07T08:12:14.510898569Z","cvss":[{"version":"3.0","score":9.8,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-502"],"updated_at":"2026-11-02T15:46:53.244788Z"},{"id":"PYSEC-2026-568","title":"vLLM deserialization vulnerability in vllm.distributed.GroupCoordinator.recv_object","description":"vllm-project vllm version 0.6.0 contains a vulnerability in the distributed training API. The function vllm.distributed.GroupCoordinator.recv_object() deserializes received object bytes using pickle.loads() without sanitization, leading to a remote code execution vulnerability.\n\n### Maintainer perspective\nNote that vLLM does NOT use the code as described in the report on huntr. The problem only exists if you use these internal APIs in a way that exposes them to a network as described. The vllm team was not involved in the analysis of this report and the decision to assign it a CVE.","status":"published","published":"2026-06-29T11:50:34.951406Z","modified":"2026-07-01T20:23:11.311128Z","cvss":[{"version":"3.0","score":9.8,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:57.671918Z"}]}}