CVE-2026-94622

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-22. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

vLLM versions through 0.29.0 contain a denial of service vulnerability in the NIXL connector's metadata handling for prefill/decode disaggregated deployments. Attackers can send requests with incomplete kv_transfer_params dictionary entries to trigger an uncaught KeyError in EngineCore scheduling, causing the decode engine to terminate and making all routed requests fail until manual restart.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
49
EG Risk 49/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 21, 2026

Last Modified

September 29, 2026

Advisory Details (4)

Auto-updated Sep 21, 2026
No patch confirmed yet. Sources: github_pr.
generic

vLLM through 0.29.0 Denial of Service via Incomplete NIXL KV Transfer Metadata | Advisories | VulnCheck

https://www.vulncheck.com/advisories/vllm-through-0.29.0-denial-of-service-via-incomplete-nixl-kv-transfer-metadata
github_pr

[Bugfix] Validate kv_transfer_params before NIXL recv registration

Upstream fix in progress (PR #54807 · vllm-project/vllm, state=open)

https://github.com/vllm-project/vllm/pull/54807
generic

vllm/vllm/distributed/kv_transfer/kv_connector/v1/nixl/metadata.py at v0.29.0 · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/metadata.py#L294-L312
generic

GitHub - vllm-project/vllm: A high-throughput and memory-efficient inference and serving engine for LLMs · GitHub

https://github.com/vllm-project/vllm

Vendor Advisories for CVE-2026-94622(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
vllm0.0.1 ... 0.9.2 (97 versions)
  • every version up to 0.30.0: fixed in 0.30.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 30× in last 7d / 63× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 01:48 UTCEG score recompute
  2. 2026-10-05 01:48 UTCGHSA enrichment
  3. 2026-10-04 23:23 UTCEPSS rescore
  4. 2026-10-04 14:46 UTCGHSA enrichment
  5. 2026-10-04 03:43 UTCGHSA enrichment
  6. 2026-10-03 16:41 UTCEG score recompute
  7. 2026-10-03 16:41 UTCGHSA enrichment
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-03 05:39 UTCGHSA enrichment
  10. 2026-10-02 18:37 UTCEG score recompute
  11. 2026-10-02 18:37 UTCGHSA enrichment
  12. 2026-10-02 17:57 UTCEPSS rescore
  13. 2026-10-02 07:33 UTCGHSA enrichment
  14. 2026-10-01 20:31 UTCEG score recompute
  15. 2026-10-01 20:31 UTCGHSA enrichment
  16. 2026-10-01 19:51 UTCEPSS rescore
  17. 2026-10-01 09:25 UTCGHSA enrichment
  18. 2026-09-30 22:24 UTCEG score recompute
  19. 2026-09-30 22:24 UTCGHSA enrichment
  20. 2026-09-30 15:04 UTCEPSS rescore
  21. 2026-09-30 11:22 UTCGHSA enrichment
  22. 2026-09-30 00:20 UTCEG score recompute
  23. 2026-09-30 00:20 UTCGHSA enrichment
  24. 2026-09-29 12:56 UTCGHSA enrichment
  25. 2026-09-29 07:44 UTCEG score recompute
Show 38 more
  1. 2026-09-29 07:44 UTCGHSA enrichment
  2. 2026-09-28 20:42 UTCEG score recompute
  3. 2026-09-28 20:42 UTCGHSA enrichment
  4. 2026-09-28 13:52 UTCEPSS rescore
  5. 2026-09-28 13:52 UTCEPSS rescore
  6. 2026-09-28 09:40 UTCGHSA enrichment
  7. 2026-09-27 22:38 UTCEG score recompute
  8. 2026-09-27 22:38 UTCGHSA enrichment
  9. 2026-09-27 13:49 UTCEPSS rescore
  10. 2026-09-27 11:35 UTCGHSA enrichment
  11. 2026-09-27 00:29 UTCEG score recompute
  12. 2026-09-27 00:29 UTCGHSA enrichment
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-26 13:27 UTCGHSA enrichment
  15. 2026-09-26 02:22 UTCEG score recompute
  16. 2026-09-26 02:21 UTCGHSA enrichment
  17. 2026-09-25 15:19 UTCGHSA enrichment
  18. 2026-09-25 04:14 UTCGHSA enrichment
  19. 2026-09-24 17:12 UTCEG score recompute
  20. 2026-09-24 17:12 UTCGHSA enrichment
  21. 2026-09-24 14:04 UTCEPSS rescore
  22. 2026-09-24 06:10 UTCGHSA enrichment
  23. 2026-09-23 19:07 UTCEG score recompute
  24. 2026-09-23 19:07 UTCGHSA enrichment
  25. 2026-09-23 17:54 UTCEPSS rescore
  26. 2026-09-23 07:34 UTCGHSA enrichment
  27. 2026-09-22 20:32 UTCEG score recompute
  28. 2026-09-22 20:32 UTCGHSA enrichment
  29. 2026-09-22 16:01 UTCEPSS rescore
  30. 2026-09-22 14:20 UTCEG score recompute
  31. 2026-09-22 14:20 UTCGHSA enrichment
  32. 2026-09-22 13:27 UTCEG score recompute
  33. 2026-09-22 13:27 UTCGHSA enrichment
  34. 2026-09-22 09:29 UTCEG score recompute
  35. 2026-09-22 09:29 UTCGHSA enrichment
  36. 2026-09-21 22:26 UTCEG score recompute
  37. 2026-09-21 22:16 UTCEG score recompute
  38. 2026-09-21 22:15 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-94622?
CVE-2026-94622 is a high vulnerability published on September 21, 2026. vLLM versions through 0.29.0 contain a denial of service vulnerability in the NIXL connector's metadata handling for prefill/decode disaggregated deployments. Attackers can send requests with incomplete kvtransferparams dictionary entries to trigger an uncaught KeyError in EngineCore scheduling,…
When was CVE-2026-94622 disclosed?
CVE-2026-94622 was first published on September 21, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-94622 actively exploited?
CVE-2026-94622 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-94622?
CVE-2026-94622 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-94622?
No fix for CVE-2026-94622 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-94622 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-94622

Explore →

Is Your Infrastructure Affected by CVE-2026-94622?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs