CVE-2026-105759: vLLM: Unbounded Prometheus label cardinality from attacker-controlled HTTP method tokens in the vLLM Rust frontend metrics middleware (unauthenticated denial of service)

Published Oct 5, 2026
·
Updated

vLLM is an inference and serving engine for large language models. Prior to 0.30.0, the Rust frontend's trackhttpmetrics 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::getorcreate 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.

Affected Software

1 affected component
vllm vllm<0.30.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade vLLM to a version that resolves this vulnerability.

    Fixed in 0.30.0

Event History

Oct 5, 2026
CVE Published
via MITRE·10:58 PM
Data Sourced
via MITRE·10:58 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

vLLM versions before 0.30.0 are affected when using the Rust frontend and requests can reach registered routes. Unguarded endpoints such as /tokenize are specifically identified as reachable attack targets.

2

What does an attacker need to exploit this issue?

An attacker does not need authentication or user interaction. They need network access to send requests using many unique arbitrary HTTP method tokens to a reachable registered route.

3

What signs indicate active exploitation or impact?

The Prometheus metrics will accumulate permanently created counter and histogram label sets for distinct HTTP method tokens. This can appear as growing process memory consumption and an increasingly large /metrics response, eventually exhausting the service or monitoring path.

4

What version contains the fix?

The issue is fixed in vLLM version 0.30.0.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203