CVE-2026-27893: CWE-693: Protection Mechanism Failure in vllm-project vllm
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.
AI Analysis
Technical Summary
The vulnerability in vLLM (CVE-2026-27893) arises because two model implementation files hardcode the parameter trust_remote_code=True when loading sub-components. This behavior overrides the user's explicit setting of --trust-remote-code=False, effectively bypassing the intended security mechanism. As a result, an attacker controlling a malicious model repository can execute arbitrary code remotely. The vulnerability affects versions from 0.10.1 up to but not including 0.18.0. Version 0.18.0 includes a patch that removes this hardcoded behavior, restoring respect for the user's security opt-out.
Potential Impact
Successful exploitation allows remote code execution with high confidentiality, integrity, and availability impact. An attacker can run arbitrary code on the system running vLLM by supplying malicious model repositories, even if the user has explicitly disabled remote code trust. This compromises system security and can lead to full system compromise.
Mitigation Recommendations
A fix is available in vLLM version 0.18.0, which patches the hardcoded trust_remote_code=True setting. Users should upgrade to version 0.18.0 or later to remediate this vulnerability. Refer to the Red Hat advisories for additional details and updates. No other mitigations are indicated by the vendor advisory.
CVE-2026-27893: CWE-693: Protection Mechanism Failure in vllm-project vllm
Description
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 v3.1
Score 8.8high
Affected software
pkg:github/vllm-project/vllmRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in vLLM (CVE-2026-27893) arises because two model implementation files hardcode the parameter trust_remote_code=True when loading sub-components. This behavior overrides the user's explicit setting of --trust-remote-code=False, effectively bypassing the intended security mechanism. As a result, an attacker controlling a malicious model repository can execute arbitrary code remotely. The vulnerability affects versions from 0.10.1 up to but not including 0.18.0. Version 0.18.0 includes a patch that removes this hardcoded behavior, restoring respect for the user's security opt-out.
Potential Impact
Successful exploitation allows remote code execution with high confidentiality, integrity, and availability impact. An attacker can run arbitrary code on the system running vLLM by supplying malicious model repositories, even if the user has explicitly disabled remote code trust. This compromises system security and can lead to full system compromise.
Mitigation Recommendations
A fix is available in vLLM version 0.18.0, which patches the hardcoded trust_remote_code=True setting. Users should upgrade to version 0.18.0 or later to remediate this vulnerability. Refer to the Red Hat advisories for additional details and updates. No other mitigations are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-24T15:19:29.717Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-27893","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:19724","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:19725","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:8748","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:8746","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:8747","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:10140","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:10141","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:24977","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:19712","vendor":"Red Hat"}]
Threat ID: 69c5c8713c064ed76fe63c5e
Added to database: 03/26/2026, 23:59:45 UTC
Last enriched: 07/30/2026, 01:38:06 UTC
Last updated: 07/31/2026, 21:26:48 UTC
Views: 407
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.