CVE-2026-53923

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 60% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

vLLM is an inference and serving engine for large language models (LLMs). From 0.5.5 until 0.23.1rc0, integer truncation of tensor dimensions in vLLM's GGUF dequantize kernels (csrc/quantization/gguf/gguf_kernel.cu) causes partial tensor processing. The output tensor is allocated at full size via torch::empty (uninitialized memory), but the dequantize CUDA kernel processes only a truncated number of elements. The unfilled portion of the output tensor retains whatever was previously in GPU memory. In multi-tenant inference deployments, this residual GPU memory may contain tensor data from other users' inference requests, constituting information disclosure. This vulnerability is fixed in 0.23.1rc0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

Published

June 17, 2026

Last Modified

June 24, 2026

Advisory Details (3)

Auto-updated Jun 23, 2026
Patch available. Sources: github_pr, github, github_commit.
githubMentions a patch (unverified)

GGUF dequantize kernel int truncation exposes uninitialized GPU memory in multi-tenant serving · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-5jv2-g5wq-cmr4
github_pr

[Security] Fix info disclosure via int32 truncation in GGUF dequantize kernels

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

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

commit f219788f9195 (vllm-project/vllm)

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

https://github.com/vllm-project/vllm/commit/f219788f91952827132fa4fdf916427cd20d225e

Vendor Advisories for CVE-2026-53923(6)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhelai3/bootc-rocm-rhel9:17882606202026-09-01redhat
redhatrhelai3/disk-image-cuda-rhel9:17882903142026-09-01redhat
redhatrhaiis/vllm-spyre-rhel9:17871617762026-08-26redhat
redhatrhaiis/vllm-cuda-rhel9:17871613822026-08-24redhat
redhatrhaiis/vllm-rocm-rhel9:17871618032026-08-24redhat
pipvllm—ghsa

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 rangeFix by version rangeDependents
vllm0.10.0 ... 0.9.2 (55 versions)
  • 0.5.5 up to 0.24.0: fixed in 0.24.0
  • 0.5.5 through 0.23.0: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 26× 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 196 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53923?
CVE-2026-53923 is a high vulnerability published on June 17, 2026. vLLM is an inference and serving engine for large language models (LLMs). From 0.5.5 until 0.23.1rc0, integer truncation of tensor dimensions in vLLM's GGUF dequantize kernels (csrc/quantization/gguf/gguf_kernel.cu) causes partial tensor processing. The output tensor is allocated at full size via…
When was CVE-2026-53923 disclosed?
CVE-2026-53923 was first published on June 17, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53923 actively exploited?
CVE-2026-53923 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53923?
CVE-2026-53923 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-53923?
A fix for CVE-2026-53923 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53923 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-53923?

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

Book a Demo →Browse All CVEs