Zero Day Monitor
DashboardVulnerabilitiesTrendingZero-DaysNews
Login
ImpressumPrivacy Policy
Zero Day Monitor © 2026
1243 articles · 105343 vulns · 38/41 feeds (7d)
← Back to list
8.8
CVE-2026-27893EXPLOITED
vllm-project · vllm

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

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.

Affected Products

VendorProductVersions
vllm-projectvllm>= 0.10.1, < 0.18.0

References

  • https://github.com/vllm-project/vllm/security/advisories/GHSA-7972-pg2x-xr59(x_refsource_CONFIRM)
  • https://github.com/vllm-project/vllm/pull/36192(x_refsource_MISC)
  • https://github.com/vllm-project/vllm/commit/00bd08edeee5dd4d4c13277c0114a464011acf72(x_refsource_MISC)

Related News (2 articles)

Tier B
BSI Advisories4h ago
[NEU] [hoch] vllm: Schwachstelle ermöglicht Codeausführung
→ No new info (linked only)
Tier C
VulDB8h ago
CVE-2026-27893 | vllm up to 0.17.x Model trust_remote_code protection mechanism (GHSA-7972-pg2x-xr59)
→ No new info (linked only)
CVSS 3.18.8 HIGH
VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CISA KEV❌ No
Actively exploited✅ Yes
CWECWE-693
Published3/26/2026
Last enriched6h agov3
Trending Score60
Source articles2
Independent2
Info Completeness9/14
Missing: epss, kev, exploit, iocs, mitre_attack

Community Vote

0
Login to vote
0 upvotes0 downvotes
No votes yet

Pin to Dashboard

Verification

State: unverified
Confidence: 0%

Version History

v3
Last enriched 6h ago
v3Tier C6h ago

Updated description with new details about the Model Handler component and clarified that no exploit is available.

description
via VulDB
v2Tier C8h ago

Updated severity to CRITICAL, marked as actively exploited, and specified patch version 0.18.0.

severityactivelyExploitedpatchAvailableaffectedVersions
via VulDB
v114h ago

Initial creation