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

High 8.8 Published Updated

Attackers can execute arbitrary code via malicious models because vLLM ignores the user's disabled remote code trust setting.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-27893?

CVE-2026-27893 is a high-severity code injection vulnerability in Vllm Vllm, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official 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.

Weakness: CWE-501, CWE-693

Which versions are affected by CVE-2026-27893?

3 open source packages ship an affected version, including vllm. It affects 1 product.

PackageAffectedFixed in
vllm PyPIFrom 0.10.10.18.0
vllm PyPIFrom 0.10.10.18.0
vllm PyPIFrom 0.10.10.18.0

Products include Vllm Vllm.

How do I fix CVE-2026-27893?

Upgrade vllm to 0.18.0 or later.

Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.

Is CVE-2026-27893 being exploited?

There is no known exploitation of CVE-2026-27893 in the wild and no public exploit code.

All Vllm Vllm vulnerabilities

Sources

Also known as GHSA-7972-pg2x-xr59, PYSEC-2026-2297.

Is CVE-2026-27893 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free