# CVE-2026-4944: Hardcoded trust_remote_code=True in vllm-project/vllm Bypasses User Security Control

> Hardcoded trust_remote_code setting in vLLM allows remote code execution via malicious models, bypassing user security controls.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** No
- **Published:** 28 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-g57c-wgqx-8wx7

## What is CVE-2026-4944?

CVE-2026-4944 is a high-severity code injection vulnerability in vllm-project/vllm, published on 28 May 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-project/vllm version 0.14.1 contains a vulnerability where the `trust_remote_code=True` parameter is hardcoded in two model implementation files (`vllm/model_executor/models/nemotron_vl.py` and `vllm/model_executor/models/kimi_k25.py`). This bypasses the user's explicit `--trust-remote-code=False` setting, enabling remote code execution via malicious HuggingFace model repositories. This issue is an incomplete fix for CVE-2025-66448 and CVE-2026-22807, as it affects separate code paths in model implementation files. Deployments loading NemotronVL or KimiK25 models are particularly impacted.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-4944?


## How do I fix CVE-2026-4944?

No fix has been published for CVE-2026-4944 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4944 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4944 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4944 and fix it if it is affected.

What it is: CVE-2026-4944 is a high-severity code injection vulnerability in vllm-project/vllm, published on 28 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4944 exists.

Affected product: vllm-project/vllm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4944/ (Markdown: https://insights.sbomify.com/CVE-2026-4944/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4944
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4944
- OSV: https://osv.dev/vulnerability/CVE-2026-4944

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4944/
Summaries are generated and may contain mistakes; the official description above is the record.