vllm-project vllm Code Injection Flaw (CVE-2026-114053) Rated CVSS 9.2
A newly published critical vulnerability in vllm-project vllm carries a CVSS score of 9.2. Here is what is affected and how to respond.
Key points
- CVE-2026-114053 affects vllm-project vllm.
- CVSS 9.2 (Critical).
- No exploitation confirmed yet.
A critical code injection tracked as CVE-2026-114053 has been published in the National Vulnerability Database for vllm-project vllm, with a CVSS base score of 9.2.
At a glance
- CVE
- CVE-2026-114053
- Product
- vllm-project vllm
- CVSS
- 9.2 Critical
- Weakness
- code injection
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: vLLM from 0.7.3 before 0.31.0 forwards the request-supplied mm_processor_kwargs.code_revision to Transformers AutoProcessor.from_pretrained, letting clients select which revision of a model's dynamic processor code is imported when trust_remote_code is enabled. An attacker controlling a revision in the served model repository can send a multimodal request to the unauthenticated /tokenize endpoint to execute arbitrary Python in the vLLM API process.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Vllm-Project | vllm | before 0.31.0 |
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-114053
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-114053?
CVE-2026-114053 is a code injection vulnerability in vllm-project vllm.
How severe is CVE-2026-114053?
It has a CVSS score of 9.2 Critical.
Is CVE-2026-114053 being exploited?
There is no public confirmation of exploitation at the time of publication.
