vLLM's hardcoded trust_remote_code=True in NemotronVL and KimiK25 bypasses user security opt-out
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.8epss 1.3%
exploitation probability
1.3%top 31% of all CVEs
observed exploitation
nono source reports it
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 · vllmReferences
https://access.redhat.com/errata/RHSA-2026:10140https://access.redhat.com/errata/RHSA-2026:10141https://access.redhat.com/errata/RHSA-2026:19712https://access.redhat.com/errata/RHSA-2026:19724https://access.redhat.com/errata/RHSA-2026:19725https://access.redhat.com/errata/RHSA-2026:24977https://access.redhat.com/errata/RHSA-2026:37275https://access.redhat.com/errata/RHSA-2026:42644https://access.redhat.com/errata/RHSA-2026:8746https://access.redhat.com/errata/RHSA-2026:8747https://access.redhat.com/errata/RHSA-2026:8748https://access.redhat.com/security/cve/CVE-2026-27893