CVE-2026-22807·Python vulnerability
vLLM is an inference and serving engine for large language models (LLMs). Starting in version 0.10.1 and prior to version 0.14.0, vLLM loads Hugging Face `auto_map` dynamic modules during model resolution without gating on `trust_remote_code`, allowing attacker-controlled Python code in a model repo/path to execute at server startup. An attacker who can influence the model repo/path (local directory or remote Hugging Face repo) can achieve arbitrary code execution on the vLLM host during model load. This happens before any request handling and does not require API access. Version 0.14.0 fixes the issue.
- Severity
- high
- Software
- Python
- Fixed in
- 0.14.0
- Published
- 2026-01-21
Affected versions
From: 0.10.1
Until: 0.14.0
Fixed in: 0.14.0
How to fix this CVE
Update vLLM to version 0.14.0 or later to prevent arbitrary code execution during model loading. The vulnerability allows untrusted Python code from Hugging Face model repositories to execute at server startup without requiring the `trust_remote_code` flag. Immediately patch all vLLM instances running versions 0.10.1 through 0.13.x, and review any model repositories used in your environment for potentially malicious code.
sudo dnf update python3-vllm || sudo pip3 install --upgrade vllm>=0.14.0Defensia detects this vulnerability
How to check if you are affected
- Check vLLM version: pip3 show vllm | grep Version or python3 -c "import vllm; print(vllm.__version__)"
- Identify model loading paths: grep -r 'auto_map\|trust_remote_code' /path/to/vllm/config or examine model configuration files for remote Hugging Face repositories
- Review server startup logs for unexpected Python module imports or execution: journalctl -u vllm -n 500 | grep -i 'import\|module\|load\|exec' or check /var/log/vllm/* for anomalies
- Verify patched version is running: pip3 show vllm | grep -E 'Version.*0\.1[4-9]|Version.*0\.[2-9]' to confirm 0.14.0 or later is installed
FAQ
What is CVE-2026-22807?
CVE-2026-22807 is a critical vulnerability in vLLM versions 0.10.1 to 0.13.x where the dynamic module loading mechanism bypasses security controls, allowing arbitrary Python code execution from untrusted model repositories during server startup without user consent.
Is CVE-2026-22807 being actively exploited?
No, this vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available, but the attack vector is straightforward and organizations should patch proactively.
What versions of vLLM are affected by CVE-2026-22807?
vLLM versions 0.10.1 through 0.13.x are vulnerable. Version 0.14.0 and later include the fix that gates auto_map module loading on the `trust_remote_code` parameter.
How do I check if my server is vulnerable to CVE-2026-22807?
Run `pip3 show vllm | grep Version` and verify the version is less than 0.14.0; if so, your deployment is vulnerable. Also confirm that model loading configurations do not explicitly enable remote code execution guards.
Does Defensia detect CVE-2026-22807?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If vLLM is installed on a monitored server, CVE-2026-22807 will appear in your dashboard with remediation steps.
Related Python CVEs
References
- https://github.com/vllm-project/vllm/commit/78d13ea9de4b1ce5e4d8a5af9738fea71fb024e5
- https://github.com/vllm-project/vllm/pull/32194
- https://github.com/vllm-project/vllm/releases/tag/v0.14.0
- https://github.com/vllm-project/vllm/security/advisories/GHSA-2pc9-4j83-qjmr
- https://access.redhat.com/errata/RHSA-2026:10184
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-22807. Free for 1 server.
Get started free