CVE-2024-9052

criticalrejectedpriority · track · 0EUUS

grimoire priorityP2 · Scheduled

Exploitable?

—

no known exploitation

Likely / severe?

— EPSS

CVSS 9.8 · critical

Is it mine?

2 products

Who says so?

3 sources

cnnvd · enisa_euvd · osv

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

cvss

Technical severity, 0–10. One row per scoring source.

9.8

010

base score 0–10 · higher = more severe · hover a vector to decode

v3.09.8criticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondary · ENISA EU

v3.09.8criticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondary · OSV

The CWE weakness classes this flaw belongs to.

Products and version ranges known to be affected.

Vendor and ecosystem advisories describing this.

GHSA-pgr7-mhp5-fgjpvLLM deserialization vulnerability in vllm.distributed.GroupCoordinator.recv_object2025-03-20ghsa · osvUS
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. ### Maintainer perspective Note 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.
PYSEC-2026-568vLLM deserialization vulnerability in vllm.distributed.GroupCoordinator.recv_object2026-06-29vendor · osvUS
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. ### Maintainer perspective Note 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.

Other names and identifiers for this entity.

Which sources assert this record, and when.

published 2025-03-20modified 2026-10-16

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.