CVE-2025-62426: vLLM vulnerable to DoS via large Chat Completion or Tokenization requests with specially crafted `chat_template_kwargs`

Published Nov 20, 2025
·
Updated

Summary The /v1/chat/completions and /tokenize endpoints allow a chattemplatekwargs request parameter that is used in the code before it is properly validated against the chat template. With the right chattemplatekwargs parameters, it is possible to block processing of the API server for long periods of time, delaying all other requests

Details In servingengine.py, the chattemplatekwargs are unpacked into kwargs passed to chatutils.py applyhfchattemplate with no validation on the keys or values in that chattemplatekwargs dict. This means they can be used to override optional parameters in the applyhfchattemplate method, such as tokenize, changing its default from False to True.

https://github.com/vllm-project/vllm/blob/2a6dc67eb520ddb9c4138d8b35ed6fe6226997fb/vllm/entrypoints/openai/servingengine.py#L809-L814

https://github.com/vllm-project/vllm/blob/2a6dc67eb520ddb9c4138d8b35ed6fe6226997fb/vllm/entrypoints/chatutils.py#L1602-L1610

Both servingchat.py and servingtokenization.py call into this preprocesschat method of servingengine.py and they both pass in chattemplatekwargs.

So, a chattemplatekwargs like {"tokenize": True} makes tokenization happen as part of applying the chat template, even though that is not expected. Tokenization is a blocking operation, and with sufficiently large input can block the API server's event loop, which blocks handling of all other requests until this tokenization is complete.

This optional tokenize parameter to applyhfchattemplate does not appear to be used, so one option would be to just hard-code that to always be False instead of allowing it to be optionally overridden by callers. A better option may be to not pass chattemplatekwargs as unpacked kwargs but instead as a dict, and only unpack them after the logic in applyhfchattemplate that resolves the kwargs against the chat template.

Impact

Any authenticated user can cause a denial of service to a vLLM server with Chat Completion or Tokenize requests.

Fix

https://github.com/vllm-project/vllm/pull/27205

Other sources

vLLM is an inference and serving engine for large language models (LLMs). From version 0.5.5 to before 0.11.1, the /v1/chat/completions and /tokenize endpoints allow a chattemplatekwargs request parameter that is used in the code before it is properly validated against the chat template. With the right chattemplatekwargs parameters, it is possible to block processing of the API server for long periods of time, delaying all other requests. This issue has been patched in version 0.11.1.

— MITRE

Affected Software

4 affected componentsFixes available
pip/vllm>=0.5.5<0.11.1
0.11.1
vllm vllm>=0.5.5<0.11.1
vllm vllm=0.11.1-rc0
vllm vllm=0.11.1-rc1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/vllm to a version that resolves this vulnerability.

    Fixed in 0.11.1
  2. Upgrade

    Upgrade vllm to a version that resolves this vulnerability.

    Fixed in 0.11.1
  3. Configuration

    Hard-code the optional tokenize parameter to False so chat_template_kwargs cannot override it.

    vLLM apply_hf_chat_template tokenize = False

Event History

Nov 20, 2025
Advisory Published
via GitHub·09:26 PM
Data Sourced
via GitHub·09:26 PM
DescriptionSeverityWeaknessAffected Software
Nov 21, 2025
CVE Published
via MITRE·01:21 AM
Data Sourced
via MITRE·01:21 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 AM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-62426?

CVE-2025-62426 has been classified as a medium severity vulnerability due to potential denial of service risks.

2

How do I fix CVE-2025-62426?

To fix CVE-2025-62426, update the vllm package to version 0.11.2 or later, ensuring proper validation of the chat_template_kwargs parameter.

3

What software versions are affected by CVE-2025-62426?

CVE-2025-62426 affects vllm versions between 0.5.5 and 0.11.1.

4

What are the consequences of exploiting CVE-2025-62426?

Exploiting CVE-2025-62426 can lead to denial of service by blocking the API server's processing capabilities.

5

What specific endpoints are vulnerable in CVE-2025-62426?

The vulnerable endpoints in CVE-2025-62426 are /v1/chat/completions and /tokenize.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203