{"answers":{"affected":"3 open source packages ship an affected version, including vllm. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11041 exists.","fix":"No fix has been published for CVE-2024-11041 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-11041 is a critical unsafe deserialization vulnerability in Vllm Vllm, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-11041 and fix it if it is affected.\n\nWhat it is: CVE-2024-11041 is a critical unsafe deserialization vulnerability in Vllm Vllm, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11041 exists.\n\nAffected packages and fixed versions:\n- vllm (PyPI): affected all versions up to 0.6.2; no fix listed\n- vllm (PyPI): affected all versions up to 0.6.2; no fix listed\n- vllm (PyPI): affected all versions up to 0.6.2; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-11041/ (Markdown: https://insights.sbomify.com/CVE-2024-11041/index.md)","id":"CVE-2024-11041","markdown":"https://insights.sbomify.com/CVE-2024-11041/index.md","name":"CVE-2024-11041","record":{"aliases":["GHSA-5vqr-wprc-cpp7","PYSEC-2026-566"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python LLM library","requires_auth":"none","summary":"An attacker can execute arbitrary code on the victim's machine by sending a malicious payload to the MessageQueue due to unsafe pickle deserialization.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"vllm","vendor":"vllm"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"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 MessageQueue, causing the victim's machine to execute arbitrary code.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Remote Code Execution in vllm-project/vllm","id":"CVE-2024-11041","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"vllm:vllm","products":["vllm:vllm"],"type":"deserialization","year":"2024"},"n_packages":3,"n_references":1,"next":{"headline":"Arbitrary File Delete in invoke-ai/invokeai","id":"CVE-2024-11042"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.6.2"],"package":"vllm","purl":null,"source":"GHSA-5vqr-wprc-cpp7"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.6.2"],"package":"vllm","purl":"pkg:pypi/vllm","source":"GHSA-5vqr-wprc-cpp7"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.6.2"],"package":"vllm","purl":"pkg:pypi/vllm","source":"PYSEC-2026-566"}],"prev":{"headline":"Deserialization of Untrusted Data in binary-husky/gpt_academic","id":"CVE-2024-11039"},"products":["vllm-project/vllm"],"published":"2025-03-20","related":[{"cvss_score":10,"headline":"vLLM Vulnerable to Remote Code Execution via Mooncake Integration","id":"CVE-2025-32444","kev_date_added":null,"published":"2025-04-30"},{"cvss_score":9.8,"headline":"vLLM leaks a heap address when PIL throws an error","id":"CVE-2026-22778","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":9.8,"headline":"vLLM Allows Remote Code Execution via PyNcclPipe Communication Service","id":"CVE-2025-47277","kev_date_added":null,"published":"2025-05-20"},{"cvss_score":9.1,"headline":"vLLM: OpenAI auth bypass","id":"CVE-2026-48746","kev_date_added":null,"published":"2026-06-22"},{"cvss_score":9.1,"headline":"vLLM Allows Remote Code Execution via Mooncake Integration","id":"CVE-2025-29783","kev_date_added":null,"published":"2025-03-19"},{"cvss_score":8.8,"headline":"vLLM 0.9.2 before 0.24.0 SSRF via X-Request-Id in P2pNcclConnector","id":"CVE-2026-116176","kev_date_added":null,"published":"2026-10-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-20","vendors":["vllm-project"]},"summary":"An attacker can execute arbitrary code on the victim's machine by sending a malicious payload to the MessageQueue due to unsafe pickle deserialization.","url":"https://insights.sbomify.com/CVE-2024-11041/"}