CVE-2026-55514

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 51% 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, nvd
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.5Exploit: None knownExposed: 0

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

vLLM is a library for LLM inference and serving. From 0.12.0 to before 0.24.0, sending a pure prompt embeds payload in a /v1/completions request with a model using M-RoPE causes EngineCore to fail an assertion and fatally crash, shutting down the entire server application. Any remote user who is authorized to make a /v1/completions request can make such a request and induce a crash. This issue is fixed in version 0.24.0.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
30(Track)
EG Risk 30/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
Severity65% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (4)

Auto-updated Jul 7, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
github Patch Available

DoS caused by sending `/v1/completions` with prompt embeds payload with models that use M-RoPE · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-33cg-gxv8-3p8g
github_release Patch Available

v0.24.0

Patch available: vllm-project/vllm v0.24.0

https://github.com/vllm-project/vllm/releases/tag/v0.24.0
github_pr

[Security] Fix DoS via prompt_embeds on M-RoPE models

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

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

commit 470229c37efa (vllm-project/vllm)

Fix landed in vllm-project/vllm commit 470229c37efa — awaiting tagged release

https://github.com/vllm-project/vllm/commit/470229c37efaf69c86e8bc97482b0b1ff7551c65

Vendor Advisories for CVE-2026-55514(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
vllm0.12.0 ... 0.23.0 (20 versions)0.24.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 52× 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-08-26 14:46 UTCEPSS rescore
  2. 2026-08-26 13:55 UTCEG score recompute
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-25 11:59 UTCEG score recompute
  5. 2026-08-24 10:01 UTCEG score recompute
  6. 2026-08-23 06:57 UTCEG score recompute
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 06:25 UTCEG score recompute
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-21 05:50 UTCEG score recompute
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-20 05:18 UTCEG score recompute
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-19 04:45 UTCEG score recompute
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-18 03:47 UTCEG score recompute
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 00:43 UTCEG score recompute
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-16 00:11 UTCEG score recompute
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-13 23:06 UTCEG score recompute
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-12 22:32 UTCEG score recompute
Show 62 more
  1. 2026-08-12 13:51 UTCEPSS rescore
  2. 2026-08-11 22:00 UTCEG score recompute
  3. 2026-08-11 00:00 UTCEPSS rescore
  4. 2026-08-09 20:55 UTCEG score recompute
  5. 2026-08-09 13:46 UTCEPSS rescore
  6. 2026-08-08 20:24 UTCEG score recompute
  7. 2026-08-08 16:37 UTCEPSS rescore
  8. 2026-08-07 19:52 UTCEG score recompute
  9. 2026-08-06 19:20 UTCEG score recompute
  10. 2026-08-06 13:47 UTCEPSS rescore
  11. 2026-08-05 19:17 UTCEPSS rescore
  12. 2026-08-04 18:16 UTCEG score recompute
  13. 2026-08-04 15:10 UTCEPSS rescore
  14. 2026-08-04 10:39 UTCEPSS rescore
  15. 2026-08-03 17:29 UTCEG score recompute
  16. 2026-08-03 10:36 UTCEPSS rescore
  17. 2026-08-02 16:42 UTCEG score recompute
  18. 2026-08-02 02:27 UTCEPSS rescore
  19. 2026-08-01 16:10 UTCEG score recompute
  20. 2026-08-01 04:16 UTCEPSS rescore
  21. 2026-07-31 15:38 UTCEG score recompute
  22. 2026-07-30 16:28 UTCEPSS rescore
  23. 2026-07-30 15:04 UTCEG score recompute
  24. 2026-07-30 01:30 UTCEPSS rescore
  25. 2026-07-29 14:24 UTCEG score recompute
  26. 2026-07-28 15:37 UTCEPSS rescore
  27. 2026-07-28 13:52 UTCEG score recompute
  28. 2026-07-27 13:19 UTCEG score recompute
  29. 2026-07-26 14:54 UTCEPSS rescore
  30. 2026-07-26 12:47 UTCEG score recompute
  31. 2026-07-25 14:18 UTCEPSS rescore
  32. 2026-07-24 14:18 UTCEPSS rescore
  33. 2026-07-23 14:18 UTCEPSS rescore
  34. 2026-07-23 03:20 UTCEG score recompute
  35. 2026-07-22 14:08 UTCEPSS rescore
  36. 2026-07-21 15:25 UTCEPSS rescore
  37. 2026-07-20 17:08 UTCEPSS rescore
  38. 2026-07-19 14:31 UTCEPSS rescore
  39. 2026-07-19 14:31 UTCEPSS rescore
  40. 2026-07-19 02:29 UTCEPSS rescore
  41. 2026-07-18 10:04 UTCEPSS rescore
  42. 2026-07-16 17:03 UTCEPSS rescore
  43. 2026-07-15 16:57 UTCEPSS rescore
  44. 2026-07-15 16:57 UTCEPSS rescore
  45. 2026-07-15 02:00 UTCEPSS rescore
  46. 2026-07-15 02:00 UTCEPSS rescore
  47. 2026-07-13 22:31 UTCEPSS rescore
  48. 2026-07-13 06:13 UTCEPSS rescore
  49. 2026-07-13 06:13 UTCEPSS rescore
  50. 2026-07-12 05:46 UTCEPSS rescore
  51. 2026-07-11 08:27 UTCEPSS rescore
  52. 2026-07-11 08:27 UTCEPSS rescore
  53. 2026-07-09 19:10 UTCEPSS rescore
  54. 2026-07-09 19:10 UTCEPSS rescore
  55. 2026-07-08 15:16 UTCEPSS rescore
  56. 2026-07-08 15:16 UTCEPSS rescore
  57. 2026-07-07 21:43 UTCEG score recompute▼ 0.60
  58. 2026-07-07 20:14 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  59. 2026-07-07 13:46 UTCEPSS rescore
  60. 2026-07-07 13:46 UTCEPSS rescore
  61. 2026-07-06 20:30 UTCEG score recompute
  62. 2026-07-06 20:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55514?
CVE-2026-55514 is a medium vulnerability published on July 6, 2026. vLLM is a library for LLM inference and serving. From 0.12.0 to before 0.24.0, sending a pure prompt embeds payload in a /v1/completions request with a model using M-RoPE causes EngineCore to fail an assertion and fatally crash, shutting down the entire server application. Any remote user who is…
When was CVE-2026-55514 disclosed?
CVE-2026-55514 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-55514 actively exploited?
CVE-2026-55514 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 50.9% of all scored CVEs.
What is the CVSS score of CVE-2026-55514?
CVE-2026-55514 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-55514?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55514, 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-55514

Explore →

Is Your Infrastructure Affected by CVE-2026-55514?

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

Start Free Scan →Browse All CVEs