Skip to content
Multiple vLLM Vulnerabilities Disclosed Affecting Versions 0.10.2 to 0.31.0

Multiple vLLM Vulnerabilities Disclosed Affecting Versions 0.10.2 to 0.31.0

First seen 25 Oct 2026, 18:12 UTC •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 25, 2026 at 19:12 UTC
  • •Three vulnerabilities in vLLM versions 0.10.2 to 0.31.0 disclosed today.
  • •Vulnerabilities include memory exhaustion, DoS attacks, and cross-tenant issues.
  • •No active exploitation reported; users should prioritize patching.

Three vulnerabilities in vLLM versions 0.10.2 to 0.31.0 have been disclosed, affecting users of the library. The first vulnerability allows for memory exhaustion via media_io_kwargs num_frames override (CWE-770). The second vulnerability enables a denial-of-service (DoS) attack through a Nemotron-VL Processor decompression bomb guard bypass (CWE-400). Lastly, a cross-tenant DoS vulnerability exists due to uninitialized logprobstensors. These vulnerabilities impact various versions of vLLM, with the earliest affected version being 0.10.2 and the latest being 0.31.0. No has been reported as of now, but users are advised to prioritize patching. GitHub Security Advisory GHSA-4m6g-h9mv-wqjc and GHSA-mm38-5g96-7j6x provide more details on the vulnerabilities.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-25
Multiple vulnerabilities disclosed
Three vulnerabilities affecting vLLM versions 0.10.2 to 0.31.0 were disclosed today, including memory exhaustion and DoS issues.
VulnCheck
2026-10-25
GitHub Security Advisory published
GitHub published advisories GHSA-4m6g-h9mv-wqjc and GHSA-mm38-5g96-7j6x detailing the vulnerabilities.
VulnCheck

More articles in this cluster (3)

Common questions

Which versions of vLLM are affected?
vLLM versions from 0.10.2 to 0.31.0 are affected by the disclosed vulnerabilities.
Is there any active exploitation of these vulnerabilities?
No active exploitation has been reported at this time.
What should users do to protect themselves?
Users should prioritize patching their vLLM installations to mitigate the disclosed vulnerabilities.