A vulnerability was found in vllm-project vLLM 0.26.0/0.27.0. Affected is the function MoRIIOConnectorScheduler.request_finished/MoRIIOConnectorWorker.get_finished/MoRIIOWrapper._handle_release_message of the file vllm/distributed/kv_transfer/kv_connector/v1/moriio/moriio_connector.py of the component MoRIIO Acknowledgement Handler. Performing a manipulation of the argument request_id/kv_transfer_params results in resource consumption. It is possible to initiate the attack remotely. The project was informed of the problem early through a pull request but has not reacted yet.
CVE-2026-92220
Score 5.3 from GitHub Security Advisory published 2026-09-16. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 39(Track)EG Risk 39/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 computedSeverity53% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 43%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 16, 2026
Advisory Details (2)
Auto-updated Sep 16, 2026GitHub - vllm-project/vllm: A high-throughput and memory-efficient inference and serving engine for LLMs · GitHub
https://github.com/vllm-project/vllm/[Bugfix] Fix MoRIIO pending ACK resource exhaustion vulnerability
Upstream fix in progress (PR #50674 · vllm-project/vllm, state=open)
https://github.com/vllm-project/vllm/pull/50674Vendor Advisories for CVE-2026-92220(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 18× 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.
- 2026-09-19 21:08 UTCEG score recompute
- 2026-09-19 21:08 UTCGHSA enrichment
- 2026-09-18 21:14 UTCEG score recompute
- 2026-09-18 21:14 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 20:56 UTCEG score recompute
- 2026-09-17 20:56 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 21:02 UTCEG score recompute
- 2026-09-16 21:02 UTCGHSA enrichment
- 2026-09-16 19:49 UTCEG score recompute
- 2026-09-16 19:49 UTCGHSA enrichment
- 2026-09-16 18:05 UTCEG score recompute
- 2026-09-16 18:05 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 03:24 UTCEG score recompute
- 2026-09-16 02:33 UTCEG score recompute
- 2026-09-16 02:32 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-92220?
When was CVE-2026-92220 disclosed?
Is CVE-2026-92220 actively exploited?
What is the CVSS score of CVE-2026-92220?
How do I remediate CVE-2026-92220?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-92220
Is Your Infrastructure Affected by CVE-2026-92220?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.