CVE-2026-93436

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-18. 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 properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
38(Track)
EG Risk 38/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

September 17, 2026

Last Modified

September 17, 2026

Advisory Details (4)

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

vLLM through 0.29.0 Memory Exhaustion via Rejected Requests | Advisories | VulnCheck

https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
generic

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

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

vllm/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.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/push_worker.py#L162-L181
github_pr

[Security] Drop leftover NIXL empty-recv metadata

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

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

Vendor Advisories for CVE-2026-93436(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 12× in last 7d / 12× 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-20 05:53 UTCGHSA enrichment
  2. 2026-09-19 19:00 UTCEG score recompute
  3. 2026-09-19 19:00 UTCGHSA enrichment
  4. 2026-09-19 08:06 UTCGHSA enrichment
  5. 2026-09-18 21:13 UTCEG score recompute
  6. 2026-09-18 21:13 UTCGHSA enrichment
  7. 2026-09-18 19:28 UTCEPSS rescore
  8. 2026-09-18 10:19 UTCEG score recompute
  9. 2026-09-18 10:19 UTCGHSA enrichment
  10. 2026-09-17 23:25 UTCEG score recompute
  11. 2026-09-17 22:25 UTCEG score recompute
  12. 2026-09-17 22:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93436?
CVE-2026-93436 is a high vulnerability published on September 17, 2026. vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
When was CVE-2026-93436 disclosed?
CVE-2026-93436 was first published in the National Vulnerability Database on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93436 actively exploited?
CVE-2026-93436 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 55.8% of all scored CVEs.
What is the CVSS score of CVE-2026-93436?
CVE-2026-93436 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-93436?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-93436, 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-93436

Explore →

Is Your Infrastructure Affected by CVE-2026-93436?

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