Cyber Resilience

CVE-2025-62372

Vllm 0.5.5 – 0.11.1

Published
21 November 2025
Modified
04 December 2025
Patch / advisory
View advisory
CVSS Score v4 8.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0037 30th percentile
Risk Priority 38 floored blend · peak EPSS

Summary

CVE-2025-62372 is a high-severity Improper Validation of Array Index (CWE-129) vulnerability in Vllm Vllm. Its CVSS base score is 8.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

This vulnerability is AI-related — categorised as NLP and Transformers; in the Data-Related Vulnerabilities risk domain.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-129

AI Security AnalysisAI

AI Category
NLP and Transformers
Risk Domain
Data-Related Vulnerabilities
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
Matched keywords: llms, vllm

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-44222Same product: Vllm Vllm
CVE-2025-62164Same product: Vllm Vllm
CVE-2026-44223Same product: Vllm Vllm
CVE-2026-34760Same product: Vllm Vllm
CVE-2025-48944Same product: Vllm Vllm
CVE-2024-11041Same product: Vllm Vllm
CVE-2025-30165Same product: Vllm Vllm
CVE-2025-32444Same product: Vllm Vllm
CVE-2025-29783Same product: Vllm Vllm
CVE-2025-24357Same product: Vllm Vllm

Affected Assets

vllm
vllm
0.11.1 · 0.5.5 — 0.11.1

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and bounds checking that prevent improper array indexing.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect out-of-bounds array access but does not prevent the weakness by itself.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and bounds checking that directly prevents improper array indexing.

A.8.26 Application security requirements partial match
prevents

Application security requirements include validation of untrusted input used for indexing or addressing memory structures.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage defensive coding patterns that reduce index-related vulnerabilities.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require bounds checking and validation of array indices derived from untrusted data.

References