cve.bz

CVE-2026-105759 vllm vllm: Uncontrolled Resource Consumption

7.5 highExploit referenceEPSS 0.4%Fix available

High (7.5) in vllm vllm. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in vllm 0.30.0.

On this page
vLLM is an inference and serving engine for large language models. Prior to 0.30.0, the Rust frontend's track_http_metrics middleware records the raw HTTP method token as a Prometheus label for requests reaching registered routes. An unauthenticated attacker can send unique arbitrary method tokens to unguarded routes such as /tokenize, causing Prometheus's Family::get_or_create function to permanently create counter and histogram label sets. Those label sets increase process memory usage and enlarge the /metrics response until the service or monitoring path is exhausted. This issue is fixed in version 0.30.0.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-105759 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105759?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105759?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105759 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
vllm:vllmbefore 0.30.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
PYSEC-2026-4325PyPIvllm<0.30.00.30.0

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A flaw of moderate impact was found in vLLM, which is shipped in Red Hat AI Inference Server, Red Hat OpenShift AI (RHOAI), and Red Hat Enterprise Linux AI (RHEL AI). The vLLM metrics-tracking middleware records the raw HTTP method token of each request as a Prometheus label without validation, normalization, or cardinality limits. An unauthenticated remote attacker can send requests with arbitrary, non-standard HTTP method names to unguarded server routes (such as /tokenize), causing the server to permanently create a new metrics label set for each unique method token received. Because these entries are never released, process memory consumption grows without bound and can eventually exhaust system resources and crash the vLLM service, while the steadily growing metrics output also places pressure on the monitoring stack. There is no impact on confidentiality or integrity. Red Hat rates this flaw as MODERATE severity with a CVSS 3.1 score of 5.9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H), matching the upstream assessment. The high attack-complexity rating reflects that exploitation requires the optional vLLM Rust frontend code path to be in use and requires an attacker to sustain a substantial volume of unique method tokens over time. All currently affected Red Hat product flows are marked AFFECTED with a resolution of DEFER: because this is a moderate-severity, availability-only issue with a CVSS score below 7.0, Red Hat is not planning an immediate fix. The residual risk is that an unauthenticated remote attacker can degrade or crash the vLLM inference service in affected deployments.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat AI Inference Serverrhaiis/vllm-cpu-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-cuda-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-neuron-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-rocm-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-spyre-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-tpu-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-cpu-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-cuda-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-gaudi-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-neuron-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-rocm-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-spyre-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-tpu-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-aws-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-azure-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-azure-rocm-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-gaudi-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-gcp-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-rocm-rhel9Fix deferred
7 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-105759.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON