CVE-2026-105922

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 4.3 from GitHub Security Advisory (severity: LOW) published 2026-10-06. A secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
4.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.3Exploit: No code on recordExposed services: Not assessed

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

The CVE record's description, written by its CNA (VulDB), states the affected versions: "A security flaw has been discovered in vllm-project vLLM up to 0.31.0." No release containing a fix is confirmed on record.

A security flaw has been discovered in vllm-project vLLM up to 0.31.0. This impacts the function get_token_bin_counts_and_mask of the file vllm/model_executor/layers/utils.py of the component Penalty Handler. Performing a manipulation results in denial of service. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

CVSS v3
4.3
EG Score
4.3MEDIUMhigh confidence
EG Risk
35
EG Risk 35/100

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 (value × EchelonGraph’s weight)
Severity43% × 45%
The EG Score, 4.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* 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, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 6, 2026

Last Modified

October 9, 2026

Advisory Details (3)

Auto-updated Oct 6, 2026
No fix on record yet.
Web page

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

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

[Bug]: `prompt_embeds` + any penalty kills the engine with a device-side assert (`scatter gather kernel index out of bounds`) · Issue #57719 · vllm-project/vllm · GitHub

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

Vendor Advisories for CVE-2026-105922(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 21× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  2. 2026-10-12 16:39 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-10-11 20:15 UTCEG score recompute
  5. 2026-10-11 18:27 UTCEG score recompute
  6. 2026-10-11 15:00 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  8. 2026-10-11 11:20 UTCEG score recompute
  9. 2026-10-11 11:19 UTCGHSA enrichmentGHSA-x9pq-jx6q-p3qv · GitHub severity LOW · GitHub CVSS 4.3
  10. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  11. 2026-10-10 13:06 UTCEG score recompute
  12. 2026-10-10 13:06 UTCGHSA enrichmentGHSA-x9pq-jx6q-p3qv · GitHub severity LOW · GitHub CVSS 4.3
  13. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-10-09 14:57 UTCGHSA enrichmentGHSA-x9pq-jx6q-p3qv · GitHub severity LOW · GitHub CVSS 4.3
  15. 2026-10-09 13:27 UTCEG score recompute
  16. 2026-10-09 13:27 UTCGHSA enrichmentGHSA-x9pq-jx6q-p3qv · GitHub severity LOW · GitHub CVSS 4.3
  17. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  18. 2026-10-08 15:17 UTCEG score recompute
  19. 2026-10-08 15:17 UTCGHSA enrichmentGHSA-x9pq-jx6q-p3qv · GitHub severity LOW · GitHub CVSS 4.3
  20. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  21. 2026-10-07 16:56 UTCGHSA enrichmentGHSA-x9pq-jx6q-p3qv · GitHub severity LOW · GitHub CVSS 4.3
  22. 2026-10-06 18:32 UTCEG score recompute
  23. 2026-10-06 18:32 UTCGHSA enrichmentGHSA-x9pq-jx6q-p3qv · GitHub severity LOW · GitHub CVSS 4.3
  24. 2026-10-06 18:31 UTCNVD updateCVSS v4 → 2.1
  25. 2026-10-06 17:47 UTCEG score recompute
Show 6 more
  1. 2026-10-06 17:47 UTCGHSA enrichmentGHSA-x9pq-jx6q-p3qv · GitHub severity LOW · GitHub CVSS 4.3
  2. 2026-10-06 17:46 UTCMITRE cvelistV5CVSS v4 → 5.3
  3. 2026-10-06 15:27 UTCEG score recompute
  4. 2026-10-06 15:25 UTCNVD updateCVSS v4 → 2.1
  5. 2026-10-06 14:55 UTCEG score recomputeFirst assessed: 4.3 MEDIUM
  6. 2026-10-06 14:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-105922?
CVE-2026-105922 is a medium-severity vulnerability; its CVE record was published on October 6, 2026. A security flaw has been discovered in vllm-project vLLM up to 0.31.0. This impacts the function gettokenbincountsandmask of the file vllm/modelexecutor/layers/utils.py of the component Penalty Handler. Performing a manipulation results in denial of service. Remote exploitation of the attack is…
When was the CVE record for CVE-2026-105922 published?
The CVE record for CVE-2026-105922 was published on October 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 9, 2026; the record at its source may have been updated since.
Is CVE-2026-105922 actively exploited?
CVE-2026-105922 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-105922?
CVE-2026-105922 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-105922?
No fix for CVE-2026-105922 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 CVE record's description, written by its CNA (VulDB), states the affected versions: "A security flaw has been discovered in vllm-project vLLM up to 0.31.0." No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-105922 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-105922?

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