CVE-2026-54234

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 52% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
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: Elevated riskExposed: 0

A fix is available — apply it.

vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. Prior to 0.24.0, a frontend-legal multi-request speculative decoding workload can cause the rejection sampler to produce a recovered token equal to the model vocabulary size boundary value, which is then converted to negative one when the engine selects the next live token for a request and is written back into the drafter's input ids; that out-of-vocabulary value is later consumed by the model's embedding and attention path and crashes the engine worker with a GPU device-side assertion. The same triggering request sequence is reachable through the public gRPC Generate and Abort endpoints, so a remote client that can send generation requests can crash the shared engine worker, aborting concurrent requests and causing a service-wide denial of service for other clients of the deployment until the worker is restarted. This issue is fixed in version 0.24.0.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (3)

Auto-updated Jul 7, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github.
github Patch Available🟡 PoC Available

Remote DoS in vLLM via Invalid Recovered Token Reinjection · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-8wr5-jm2h-8r4f
github_pr

[Security] Fix remote DoS via invalid recovered token reinjection

Fix merged in vllm-project/vllm PR #44744 on 2026-06-10 — awaiting tagged release

https://github.com/vllm-project/vllm/pull/44744
github_commit

commit 8a5cf1ccd65e (vllm-project/vllm)

Fix landed in vllm-project/vllm commit 8a5cf1ccd65e — awaiting tagged release

https://github.com/vllm-project/vllm/commit/8a5cf1ccd65e8ac7635c402c1ec0b08988bc26ca

Vendor Advisories for CVE-2026-54234(4)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhaiis/vllm-cuda-rhel9:17878605802026-08-31redhat
redhatrhaiis/vllm-rocm-rhel9:17878848732026-08-31redhat
redhatrhaiis/vllm-spyre-rhel9:17871617762026-08-26redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
vllm0.17.1 ... 0.23.0 (12 versions)0.24.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 48× 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.

Showing the most recent 100 of 126 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 05:59 UTCEG score recompute
  3. 2026-09-18 05:59 UTCVendor advisory
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-14 11:39 UTCVendor advisory
  8. 2026-09-13 23:56 UTCEG score recompute
  9. 2026-09-13 23:56 UTCVendor advisory
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-13 08:43 UTCEG score recompute
  12. 2026-09-13 08:43 UTCVendor advisory
  13. 2026-09-12 13:36 UTCEG score recompute
  14. 2026-09-12 13:36 UTCVendor advisory
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-10 09:35 UTCEPSS rescore
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-07 16:01 UTCEPSS rescore
  19. 2026-09-06 14:10 UTCEG score recompute
  20. 2026-09-06 14:10 UTCVendor advisory
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-05 23:07 UTCEG score recompute
  23. 2026-09-05 23:07 UTCVendor advisory
  24. 2026-09-04 05:06 UTCEPSS rescore
  25. 2026-09-02 14:12 UTCEPSS rescore
Show 75 more
  1. 2026-09-01 13:54 UTCEPSS rescore
  2. 2026-09-01 04:40 UTCEPSS rescore
  3. 2026-08-30 19:17 UTCEPSS rescore
  4. 2026-08-30 19:15 UTCVendor advisory
  5. 2026-08-30 08:02 UTCEG score recompute
  6. 2026-08-30 08:02 UTCVendor advisory
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-27 21:58 UTCEG score recompute
  10. 2026-08-27 21:58 UTCVendor advisory
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 02:12 UTCEG score recompute
  13. 2026-08-27 02:12 UTCVendor advisory
  14. 2026-08-26 14:46 UTCEPSS rescore
  15. 2026-08-26 13:55 UTCEG score recompute
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-24 15:18 UTCEG score recompute
  18. 2026-08-23 05:21 UTCEG score recompute
  19. 2026-08-23 00:19 UTCEPSS rescore
  20. 2026-08-22 04:48 UTCEG score recompute
  21. 2026-08-21 23:49 UTCEPSS rescore
  22. 2026-08-21 04:17 UTCEG score recompute
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-20 02:27 UTCEG score recompute
  25. 2026-08-19 17:04 UTCEPSS rescore
  26. 2026-08-18 22:29 UTCEG score recompute
  27. 2026-08-18 13:48 UTCEPSS rescore
  28. 2026-08-17 22:40 UTCEG score recompute
  29. 2026-08-17 13:47 UTCEPSS rescore
  30. 2026-08-16 20:29 UTCEG score recompute
  31. 2026-08-16 14:56 UTCEPSS rescore
  32. 2026-08-16 09:18 UTCEG score recompute
  33. 2026-08-16 02:14 UTCEPSS rescore
  34. 2026-08-15 10:56 UTCEG score recompute
  35. 2026-08-15 01:30 UTCEPSS rescore
  36. 2026-08-14 01:22 UTCEG score recompute
  37. 2026-08-13 22:00 UTCEPSS rescore
  38. 2026-08-12 15:49 UTCEG score recompute
  39. 2026-08-12 13:51 UTCEPSS rescore
  40. 2026-08-11 17:27 UTCEG score recompute
  41. 2026-08-11 06:14 UTCEG score recompute
  42. 2026-08-11 00:00 UTCEPSS rescore
  43. 2026-08-09 20:40 UTCEG score recompute
  44. 2026-08-09 13:46 UTCEPSS rescore
  45. 2026-08-08 22:18 UTCEG score recompute
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-07 23:54 UTCEG score recompute
  48. 2026-08-06 14:21 UTCEG score recompute
  49. 2026-08-06 13:47 UTCEPSS rescore
  50. 2026-08-06 03:09 UTCEG score recompute
  51. 2026-08-05 19:17 UTCEPSS rescore
  52. 2026-08-05 01:27 UTCEG score recompute
  53. 2026-08-04 15:10 UTCEPSS rescore
  54. 2026-08-04 14:04 UTCEG score recompute
  55. 2026-08-04 10:39 UTCEPSS rescore
  56. 2026-08-03 15:36 UTCEG score recompute
  57. 2026-08-03 10:36 UTCEPSS rescore
  58. 2026-08-02 06:02 UTCEG score recompute
  59. 2026-08-02 02:27 UTCEPSS rescore
  60. 2026-08-01 07:39 UTCEG score recompute
  61. 2026-08-01 04:16 UTCEPSS rescore
  62. 2026-07-30 21:57 UTCEG score recompute
  63. 2026-07-30 16:28 UTCEPSS rescore
  64. 2026-07-30 09:45 UTCEG score recompute
  65. 2026-07-30 01:30 UTCEPSS rescore
  66. 2026-07-29 00:08 UTCEG score recompute
  67. 2026-07-28 15:37 UTCEPSS rescore
  68. 2026-07-28 00:43 UTCEG score recompute
  69. 2026-07-26 23:59 UTCEG score recompute
  70. 2026-07-26 14:54 UTCEPSS rescore
  71. 2026-07-26 12:47 UTCEG score recompute
  72. 2026-07-25 14:18 UTCEPSS rescore
  73. 2026-07-24 14:18 UTCEPSS rescore
  74. 2026-07-23 14:18 UTCEPSS rescore
  75. 2026-07-23 03:19 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54234?
CVE-2026-54234 is a high vulnerability published on July 6, 2026. vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. Prior to 0.24.0, a frontend-legal multi-request speculative decoding workload can cause the rejection sampler to produce a recovered token equal to the model vocabulary size boundary value, which is then converted…
When was CVE-2026-54234 disclosed?
CVE-2026-54234 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54234 actively exploited?
CVE-2026-54234 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 51.9% of all scored CVEs.
What is the CVSS score of CVE-2026-54234?
CVE-2026-54234 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-54234?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54234, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-54234?

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

Start Free Scan →Browse All CVEs