CVE-2026-7141: vLLM makes Use of Uninitialized Resource

CVE-2026-7141 · Severity: medium · CVSS 5.6 · Published 2026-04-27

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 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."

Technologies: vllm (PyPI), Vllm. Vendors: PyPI, Vllm.

Quick answers

Is CVE-2026-7141 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-7141 being exploited in the wild.
How severe is CVE-2026-7141?
Medium severity, with a CVSS score of 5.6, published 27 April 2026.
Which products and versions are affected?
vllm (PyPI) ECOSYSTEM:introduced=0,fixed=0.19.1.
Is there a fix for CVE-2026-7141?
Yes. vllm (PyPI): upgrade to 0.19.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-7141?
Check whether you run vllm (PyPI) or Vllm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • vllm (PyPI): upgrade to 0.19.1 or later
    pip install "vllm>=0.19.1"

Affected products

  • vllm (PyPI) ECOSYSTEM:introduced=0,fixed=0.19.1
  • Vllm

Identifiers

  • CVE-2026-7141
  • GHSA-x368-4g9h-fvv4
  • PYSEC-2026-2306

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.