CVE-2024-9053: Remote Code Execution in vllm-project/vllm

Published Mar 20, 2025
·
Updated

vllm-project vllm version 0.6.0 contains a vulnerability in the AsyncEngineRPCServer() RPC server entrypoints. The core functionality runserverloop() calls the function makehandlercoro(), which directly uses cloudpickle.loads() on received messages without any sanitization. This can result in remote code execution by deserializing malicious pickle data.

Affected Software

3 affected components
vllm-project vllm
vllm-project vllm=0.6.0
pip/vllm<=0.6.0

Event History

Mar 20, 2025
CVE Published
via MITRE·10:09 AM
Data Sourced
via MITRE·10:09 AM
DescriptionSeverityWeakness
Advisory Published
via GitHub·12:32 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-9053?

CVE-2024-9053 is considered a high-severity vulnerability due to its potential for remote code execution.

2

How do I fix CVE-2024-9053?

To fix CVE-2024-9053, upgrade to a patched version of the vllm library that includes sanitization of inputs before handling.

3

What are the risks associated with CVE-2024-9053?

The risks associated with CVE-2024-9053 include remote code execution, data loss, and unauthorized system access.

4

What versions of vllm are affected by CVE-2024-9053?

CVE-2024-9053 affects vllm version 0.6.0 specifically.

5

How can I prevent exploitation of CVE-2024-9053?

To prevent exploitation of CVE-2024-9053, ensure that your application does not expose vulnerable RPC server entrypoints or use appropriate input validation techniques.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203