Advisory record · GHSA-5jv2-g5wq-cmr4

vLLM: GGUF dequantize kernel int truncation exposes uninitialized GPU memory in multi-tenant serving

CVSS 5.3 MediumEPSS 0.0048 · 41st percentile

Published by the GitHub Advisory Database at 17 Jun 2026, 14:03 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
vllmPyPI>=0.5.5, <0.24.00.24.0
Identifiers
GHSA-5jv2-g5wq-cmr4 · CVE-2026-53923 · PYSEC-2026-3403
Weakness (CWE)
CWE-200 · CWE-681
Published
17 Jun 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Affected: vLLM versions from 0.5.5 before 0.24.0 (PyPI vllm). Integer truncation in the GGUF dequantize CUDA kernels can leave part of a tensor's output buffer unwritten, so it retains stale GPU memory that may contain data from other users' requests in multi-tenant serving. An attacker who supplies a crafted GGUF model file with very large tensor dimensions could cause this when a victim loads the model, leading to information disclosure. Upgrade to vLLM 0.24.0 or later. The source gives no workaround.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0048, the 41st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:11 UTC First seen by agentprime
  2. 31 Oct 2026, 14:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.