CVE-2026-27893highCWE-501CWE-693

CVE-2026-27893: high-severity vulnerability in vllm-project vllm

vLLM's hardcoded trust_remote_code=True in NemotronVL and KimiK25 bypasses user security opt-out

Published · Updated

Follow this CVE+ Monitor vllm+ Monitor vllm

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

21Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 8.8epss 1.4%
vLLM is an inference and serving engine for large language models (LLMs). Starting in version 0.10.1 and prior to version 0.18.0, two model implementation files hardcode `trust_remote_code=True` when loading sub-components, bypassing the user's explicit `--trust-remote-code=False` security opt-out. This enables remote code execution via malicious model repositories even when the user has explicitly disabled remote code trust. Version 0.18.0 patches the issue.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Affected products
vllm-project · vllm
Related CVEs — vllm-project vllm

In the same product, most dangerous first.

CVE-2026-22778CRITICALvLLM leaks a heap address when PIL throws an errorEPSS 18.3%CVE-2025-32444CRITICALvLLM Vulnerable to Remote Code Execution via Mooncake IntegrationEPSS 1.8%CVE-2026-48746CRITICALvLLM: OpenAI auth bypassEPSS 1.2%CVE-2026-22807HIGHvLLM affected by RCE via auto_map dynamic module loading during model initializationEPSS 1.0%CVE-2025-47277CRITICALvLLM Allows Remote Code Execution via PyNcclPipe Communication ServiceEPSS 1.0%CVE-2025-62164HIGHVLLM deserialization vulnerability leading to DoS and potential RCEEPSS 1.0%