Cyber Resilience

CVE-2024-11041

RCE in Vllm 0.6.2

Published
20 March 2025
Modified
31 July 2025
CVSS Score v3 9.8
Click a component to see what it means
Raw vectorCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.014 70th percentile
Risk Priority 78 floored blend · peak EPSS

Summary

CVE-2024-11041 is a critical-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Vllm Vllm. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 30% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

This vulnerability is AI-related — categorised as NLP and Transformers; in the Supply Chain and Deployment risk domain.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

vllm-project vllm version v0.6.2 contains a deserialization flaw in the MessageQueue.dequeue() function. The routine passes data received over sockets directly to pickle.loads without validation or authentication checks, enabling arbitrary code execution when untrusted input is processed. The issue is tracked as CWE-502 and carries a CVSS 3.0 score of 9.8.

An unauthenticated remote attacker can connect to an exposed MessageQueue endpoint and transmit a crafted payload that results in immediate code execution on the target host with the privileges of the vllm process. No user interaction or special network position is required.

The single reference points to a huntr.dev bounty report that disclosed the pickle usage; no vendor advisory or patch information is supplied in the available data. The associated EPSS scores remain low and essentially flat.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

vllm-project vllm version v0.6.2 contains a vulnerability in the MessageQueue.dequeue() API function. The function uses pickle.loads to parse received sockets directly, leading to a remote code execution vulnerability. An attacker can exploit this by sending a malicious payload to the…

more

MessageQueue, causing the victim's machine to execute arbitrary code.

CWE(s)

AI Security AnalysisAI

AI Category
NLP and Transformers
Risk Domain
Supply Chain and Deployment
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
Matched keywords: vllm

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-30165Same product: Vllm Vllm
CVE-2025-32444Same product: Vllm Vllm
CVE-2025-29783Same product: Vllm Vllm
CVE-2025-47277Same product: Vllm Vllm
CVE-2025-24357Same product: Vllm Vllm
CVE-2025-62164Same product: Vllm Vllm
CVE-2026-34760Same product: Vllm Vllm
CVE-2025-48944Same product: Vllm Vllm
CVE-2026-44222Same product: Vllm Vllm
CVE-2026-44223Same product: Vllm Vllm

Affected Assets

vllm
vllm
0.6.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can uncover deserialization flaws before deployment.

Input validation directly stops deserialization of untrusted data by ensuring inputs are valid before processing.

Engineering principles such as safe deserialization and input sanitization structurally prevent the weakness from being introduced.

Integrity verification tools can detect malformed or tampered serialized data after the fact.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-02 none match
prevents

PR.PS-02 addresses only post-deployment updates/patching and cannot prevent introduction of unsafe deserialization code, yet it can remediate some instances when the flaw exists in outdated libraries or components.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing includes validation of deserialization routines and the use of untrusted data, reducing the likelihood that unsafe object reconstruction will be deployed.

prevents

Requiring vetted libraries, regular updates and SAST before release reduces the likelihood that deserialization logic will accept and act on attacker-controlled serialized objects.

finds

Regular scanning of third-party libraries and timely patching reduce the likelihood that unsafe deserialization vulnerabilities remain active.

none

Mandatory malware scanning of data received over networks or storage media intercepts malicious serialized payloads before they are deserialized by the target application.

References