Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-94627: vLLM Mooncake connector through 0.29.0 fails to properly manage GPU KV cache block ownership when concurrent c

44
This month
HIGH 7.5REMOTEUPGRADE

CVE-2026-94627 is a high-severity flaw (CVSS 7.5) affecting vllm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

vLLM Mooncake connector through 0.29.0 fails to properly manage GPU KV cache block ownership when concurrent child requests share a single transfer ID in prefill/decode disaggregated deployments. Attackers can trigger GPU memory exhaustion by submitting completion requests with multiple prompts, causing orphaned KV cache blocks to accumulate until process restart and eventually preventing legitimate requests from executing.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.6% (top 50%)
CISA exploited listNo
WeaknessCWE-401
Published2026-09-21
Last modified2026-09-29
Publisher (CNA): VulnCheck · Vendor: vllm

Share: LinkedIn · X · Reddit

Last updated 2026-09-29 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

vllm vllm UPGRADE
Affected: <= 0.29.0
Fixed in: newer than 0.29.0
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy vllm || rpm -q vllm || vllm --version
2. UPGRADE to newer than 0.29.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade vllm
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade vllm
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-94627?

vllm: upgrade to newer than 0.29.0. Exact commands for each OS are on this page.

Is CVE-2026-94627 being exploited?

CVE-2026-94627 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-94627 affect?

CVE-2026-94627 affects vllm. Severity is high (CVSS 7.5). vLLM Mooncake connector through 0.29.0 fails to properly manage GPU KV cache block ownership when concurrent child requests share a single transfer ID in prefill/decode disaggregated deployments. Attackers can trigger GPU memory exhaustion

How urgent is CVE-2026-94627?

Priority 44/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.