CVE-2026-278938.8HighCWE-693

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

vllm-project · vllm

Vendor fix available · Affected: vllm-project · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.4%probability of exploitation in the next 30 days

72nd percentile

050100

Higher than 72% of scored CVEs

8.8HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

vllm-project · vllm>= 0.10.1, < 0.18.0

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Protection Mechanism Failure · Misconfiguration and Insecure Design
Vendor: vllm-project
Published: March 2026
Band: Possible (1 to 10%), March 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-27893 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

5 more references are in the CVE record.