CVE-2026-115918: vLLM: Responses API bypasses trust_request_chat_template for chat_template_kwargs
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.
References
- github.com/advisories/GHSA-x567-49g5-p4cf
- github.com/vllm-project/vllm/commit/cff08b461e086523cee8bba5bd3c66d302625134
- github.com/vllm-project/vllm/pull/50300
- github.com/vllm-project/vllm/releases/tag/v0.32.0
- github.com/vllm-project/vllm/security/advisories/GHSA-x567-49g5-p4cf
- nvd.nist.gov/vuln/detail/CVE-2026-115918
Code Behaviors & Features
Detect and mitigate CVE-2026-115918 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →