CVE-2026-115918: vLLM: Responses API bypasses trust_request_chat_template for chat_template_kwargs
Summary vLLM's /v1/responses endpoint accepts request-level chattemplatekwargs, but does not apply the --trust-request-chat-template gate that protects Chat Completions, render, tokenize, and pooling paths. When the server is run with the documented default trustrequestchattemplate=False and no explicit --chat-template, a Responses request can pass: That key is preserved by ChatParams.getapplychattemplatekwargs()…
Published Oct 28, 2026
Affected packages
vllm
- Ecosystem
- PyPI
- Affected
- >= 0.16.0, < 0.32.0
- Fixed in
- 0.32.0
- Check
pip show vllm
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
vLLM's /v1/responses endpoint accepts request-level chat_template_kwargs, but does not apply the --trust-request-chat-template gate that protects Chat Completions, render, tokenize, and pooling paths.
When the server is run with the documented default trust_request_chat_template=False and no explicit --chat-template, a Responses request can pass:
{"chat_template_kwargs": {"chat_template": "<attacker Jinja template>"}}That key is preserved by ChatParams.get_apply_chat_template_kwargs() and then bound as the chat_template parameter to the shared HF renderer. Prior vLLM advisories establish that request-controlled Jinja chat templates can cause CPU/memory exhaustion. This report covers the current-head Responses sibling path missed by the earlier fixes.
Technical Details
The shared OpenAI frontend has a validation helper that rejects request-supplied chat templates unless the trust flag is enabled. It explicitly checks both top-level chat_template and chat_template_kwargs["chat_template"].
Responses is a separate serving path:
vllm/entrypoints/openai/responses/protocol.pyexposeschat_template_kwargs.ResponsesRequest.build_chat_params()merges request kwargs.OpenAIServingResponses._effective_chat_template_kwargs()uses those kwargs.ChatParams.get_apply_chat_template_kwargs()preserves a requestchat_templatekey when the server chat template isNone.vllm/renderers/hf.pyunpacks the result intosafe_apply_chat_template.
There is no equivalent trust gate in vllm/entrypoints/openai/responses/serving.py.
Impact
An authenticated caller who can submit /v1/responses requests can supply a request-controlled Jinja chat template despite the trust flag being disabled. The expected fixed behavior is the same as Chat Completions: reject chat_template_kwargs["chat_template"] unless the server was started with --trust-request-chat-template.
Suggested Fix
- Add
trust_request_chat_templatetoOpenAIServingResponses. - Pass
args.trust_request_chat_templatewhen constructing the Responses serving object. - Reject
request.chat_template_kwargs["chat_template"]before rendering when trust is false. - Keep ordinary kwargs such as
enable_thinkingworking. - Add regression tests for default-deny and opt-in-allow behavior on
/v1/responses.
Affected Package/Versions
Source sweep found the affected shape in:
v0.16.0v0.18.0v0.20.0v0.21.0v0.22.0v0.22.1v0.23.0- current checkout
470229c37efaf69c86e8bc97482b0b1ff7551c65 - current
origin/mainb3f0a0a0df76dda92ec4b2c9335f77e84adad911
Suggested affected range:
>= 0.16.0, <= 0.23.0Appendix: Duplicate Research
This is related to, but distinct from:
GHSA-6fvq-23cw-5628/CVE-2025-61620GHSA-69j4-grxj-j64p/CVE-2025-62426
Those advisories establish the security impact of request-controlled Jinja templates and chat_template_kwargs, but they cover older Chat Completions/tokenize implementations. This report covers a current /v1/responses sibling path that still lacks the trust gate.
Local prior submissions this report..029 do not cover this root cause.
This advisory was fixed in MR50300.
Credited to rexpository, jperezdealgaba.
References
- https://github.com/vllm-project/vllm/security/advisories/GHSA-x567-49g5-p4cf
- https://nvd.nist.gov/vuln/detail/CVE-2026-115918
- https://github.com/vllm-project/vllm/pull/50300
- https://github.com/vllm-project/vllm/commit/cff08b461e086523cee8bba5bd3c66d302625134
- https://github.com/vllm-project/vllm/releases/tag/v0.32.0
- https://github.com/advisories/GHSA-x567-49g5-p4cf
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
Coverage on the Beam blog
More vLLM vulnerabilities
All vLLM entriesCVE-2026-115911
vLLM: DoS via unbounded chat_template Jinja2 rendering exhausts the renderer thread pool
medium6.5Oct 28, 2026CVE-2026-115912
vLLM: Public multimodal SHM handle forgery reaches worker-side `pickle.loads()` with insecure serialization disabled
high7.5Oct 28, 2026CVE-2026-115913
vLLM: Phi-4 multimodal audio encoder materializes and retains full attention matrices: a single max-length audio OOM-crashes the vLLM engine
medium6.5Oct 28, 2026CVE-2026-115914
vLLM DeepSeek-OCR image processing vulnerable to denial of service
medium6.5Oct 28, 2026CVE-2026-115915
vLLM: Untrusted EPS inputs can trigger denial of service or Ghostscript RCE
high8.1Oct 28, 2026CVE-2026-115916
vLLM: Out-of-vocabulary prompt token id passes input validation and triggers a CUDA device-side assert (engine crash / DoS)
medium6.5Oct 28, 2026
