Cyber Resilience

CVE-2026-7141

Vllm ≤ 0.19.0

Published
27 April 2026
Modified
25 August 2026
CVSS Score v4 2.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/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.0029 21th percentile
Risk Priority 24 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-7141 is a low-severity Use of Uninitialized Resource (CWE-908) vulnerability in Vllm Vllm. Its CVSS base score is 2.9 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 21th 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.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A vulnerability was found in vLLM up to 0.19.0. The affected element is the function has_mamba_layers of the file vllm/v1/kv_cache_interface.py of the component KV Block Handler. Performing a manipulation results in uninitialized resource. It is possible to initiate the attack…

more

remotely. The attack is considered to have high complexity. The exploitability is described as difficult. The exploit has been made public and could be used. The existence of this vulnerability is still disputed at present. The proposed patch did not fix the issue. A 3rd party explains: "The divergence could be explained by a benign and expected vLLM behavior where vLLM server could group concurrent requests together resulting in different input shapes based on varying request arrival time. The differences in grouped input shapes could call different kernels with could produce difference results due to rounding and differences in order of operations. There is an environment variable VLLM_BATCH_INVARIANT=1 for users that desire to have deterministic output with temperature 0.0."

CWE(s)
CWE-908

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: vllm

Related Threats

MITRE ATT&CK Enterprise Techniques

T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-46722Same product: Vllm Vllm
CVE-2026-44222Same product: Vllm Vllm
CVE-2026-44223Same product: Vllm Vllm
CVE-2025-62372Same product: Vllm Vllm
CVE-2026-22778Same product: Vllm Vllm
CVE-2025-62164Same product: Vllm Vllm
CVE-2026-34756Same product: Vllm Vllm
CVE-2026-24779Same product: Vllm Vllm
CVE-2025-30202Same product: Vllm Vllm
CVE-2026-22773Same product: Vllm Vllm

Affected Assets

vllm
vllm
≤ 0.19.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including static analysis) can find uses of uninitialized resources after they are coded.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented development standards and tools can mandate initialization checks and safe patterns that stop the weakness from being introduced.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require explicit resource initialization before use, structurally avoiding uninitialized access.

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 activities such as static analysis and code review directly prevent use of uninitialized resources while also addressing many other weaknesses.

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 and acceptance can detect uninitialized resource usage through dynamic analysis and fuzzing.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates initialization checks and static analysis that can catch uninitialized resource use.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify mandatory initialization of variables and resources before use.

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

Secure system architecture and engineering principles include defensive coding practices that prevent use of uninitialized memory or objects.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require explicit initialization of all variables and resources, substantially mitigating CWE-908.

References