CVE-2026-94626

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 — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

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

vLLM through 0.29.0 fails to validate the tp_size parameter in kv_transfer_params on OpenAI-compatible completion endpoints, allowing attackers to allocate unbounded memory. Attackers can supply arbitrary tp_size values in prefill/decode disaggregated deployments to exhaust memory and trigger kernel OOM-kill of the decode worker process.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

September 21, 2026

Last Modified

September 24, 2026

Advisory Details (5)

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

vLLM through 0.29.0 Memory Exhaustion via Unvalidated NIXL tp_size | Advisories | VulnCheck

https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-unvalidated-nixl-tp-size
github_pr

fix(security): bound kv_transfer_params to prevent OOM via unbounded tp_size

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

https://github.com/vllm-project/vllm/pull/51137
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#L277
generic

vllm/vllm/distributed/kv_transfer/kv_connector/utils.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/utils.py#L569-L573
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-94626(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 20× 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-09-24 23:37 UTCEG score recompute
  2. 2026-09-24 23:37 UTCGHSA enrichment
  3. 2026-09-24 23:02 UTCEG score recompute
  4. 2026-09-24 23:02 UTCGHSA enrichment
  5. 2026-09-24 18:09 UTCEG score recompute
  6. 2026-09-24 18:09 UTCGHSA enrichment
  7. 2026-09-24 14:04 UTCEPSS rescore
  8. 2026-09-24 06:45 UTCGHSA enrichment
  9. 2026-09-23 19:21 UTCEG score recompute
  10. 2026-09-23 19:21 UTCGHSA enrichment
  11. 2026-09-23 17:54 UTCEPSS rescore
  12. 2026-09-23 07:57 UTCGHSA enrichment
  13. 2026-09-22 20:32 UTCEG score recompute
  14. 2026-09-22 20:32 UTCGHSA enrichment
  15. 2026-09-22 16:01 UTCEPSS rescore
  16. 2026-09-22 09:50 UTCEG score recompute
  17. 2026-09-22 09:50 UTCGHSA enrichment
  18. 2026-09-21 22:26 UTCEG score recompute
  19. 2026-09-21 22:16 UTCEG score recompute
  20. 2026-09-21 22:15 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-94626?
CVE-2026-94626 is a high vulnerability published on September 21, 2026. vLLM through 0.29.0 fails to validate the tpsize parameter in kvtransferparams on OpenAI-compatible completion endpoints, allowing attackers to allocate unbounded memory. Attackers can supply arbitrary tpsize values in prefill/decode disaggregated deployments to exhaust memory and trigger kernel…
When was CVE-2026-94626 disclosed?
CVE-2026-94626 was first published in the National Vulnerability Database on September 21, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-94626 actively exploited?
CVE-2026-94626 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.1% of all scored CVEs.
What is the CVSS score of CVE-2026-94626?
CVE-2026-94626 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-94626?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-94626, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-94626

Explore →

Is Your Infrastructure Affected by CVE-2026-94626?

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

Book a Demo →Browse All CVEs