mediumCVSS 5.6NVD status: Modified

CVE-2026-7141

vLLM: A vulnerability was found in vLLM up to 0.19.0.

ComponentvLLM
Severitymedium (CVSS 5.6)
CVSS vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
Published (NVD)2026-04-27
Last modified2026-08-25
Affected versions
vllm <= 0.19.0
Fixed insee the vendor advisory
WeaknessCWE-908
CISA KEVnot listed

NVD description

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

Does CVE-2026-7141 hit the version you run?Paste your docker-compose.yml, requirements.txt or package.json. The scanner checks your pinned versions against this CVE and every other one we track for vLLM.
Check my stack

What to do

  • NVD lists no fixed version yet: follow the vendor advisory below and keep vLLM off the public internet until a fix ships.
  • Do not expose the component's API or UI to the internet without authentication in front of it.

Sources

Read more

Other vLLM CVEs

All vLLM CVEs