CVE-2025-62372: vLLM vulnerable to DoS with incorrect shape of multimodal embedding inputs

Published Nov 20, 2025
·
Updated

Summary

Users can crash the vLLM engine serving multimodal models by passing multimodal embedding inputs with correct ndim but incorrect shape (e.g. hidden dimension is wrong), regardless of whether the model is intended to support such inputs (as defined in the Supported Models page).

The issue has existed ever since we added support for image embedding inputs, i.e. #6613 (released in v0.5.5)

Details

Using image embeddings as an example:

- For models that support image embedding inputs, the engine crashes when scattering the embeddings to inputsembeds (mismatched shape) - For models that don't support image embedding inputs, the engine crashes when validating the inputs inside getinputembeddings (validation fails).

This happens because we only validate ndim of the tensor, but not the full shape, in input processor (via MultiModalDataParser).

Impact

- Denial of service by crashing the engine

Mitigation

- Use API key to limit access to trusted users. - Set --limit-mm-per-prompt to 0 for all non-text modalities to ban multimodal inputs, which includes multimodal embedding inputs. However, the model would then only accept text, defeating the purpose of using a multi-modal model.

Resolution

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

Other sources

vLLM is an inference and serving engine for large language models (LLMs). From version 0.5.5 to before 0.11.1, users can crash the vLLM engine serving multimodal models by passing multimodal embedding inputs with correct ndim but incorrect shape (e.g. hidden dimension is wrong), regardless of whether the model is intended to support such inputs (as defined in the Supported Models page). 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

Event History

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

Frequently Asked Questions

1

What is the severity of CVE-2025-62372?

The severity of CVE-2025-62372 is considered high due to its potential to crash the vLLM engine.

2

How do I fix CVE-2025-62372?

To fix CVE-2025-62372, ensure you upgrade the vLLM package to version 0.11.1 or later.

3

What causes CVE-2025-62372?

CVE-2025-62372 is caused by the acceptance of multimodal embedding inputs with incorrect shapes leading to crashes.

4

Which software versions are affected by CVE-2025-62372?

CVE-2025-62372 affects vLLM versions between 0.5.5 and 0.11.1.

5

Is CVE-2025-62372 applicable to all multimodal models?

No, CVE-2025-62372 affects only those multimodal models that do not properly validate input shapes.

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