Quick answers
- Is CVE-2026-105759 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105759 being exploited in the wild.
- How severe is CVE-2026-105759?
- Medium severity, with a CVSS score of 5.9, published 5 October 2026.
- Which products and versions are affected?
- vllm (PyPI) ECOSYSTEM:introduced=0,fixed=0.30.0; vLLM Project vllm prior to 0.30.0.
- Is there a fix for CVE-2026-105759?
- Yes. vllm (PyPI): upgrade to 0.30.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105759 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-105759?
- Check whether you run vllm (PyPI) or vLLM Project vllm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- vllm (PyPI): upgrade to 0.30.0 or later
pip install "vllm>=0.30.0"
Technical details
The track_http_metrics middleware in vLLM's Rust frontend records HTTP method values directly as Prometheus labels without normalization. An unauthenticated attacker can send crafted HTTP requests with arbitrary method tokens to unguarded routes, causing Prometheus's Family::get_or_create to permanently allocate new counter and histogram label sets for each unique method value, leading to unbounded memory consumption and metric response bloat.
Affected products
- vLLM Project vLLM prior to 0.30.0
Identifiers
- CVE-2026-105759
- GHSA-5fj9-pfhr-6j48
- PYSEC-2026-4325
Timeline
- 2026-10-05: disclosed
- 2026-09-10: patched