vllm-project vllm up to 0.29.0 thinking_budget_state.py algorithmic complexity

Summaryinfo

A vulnerability marked as problematic has been reported in vllm-project vllm up to 0.29.0. This affects an unknown part of the file vllm/v1/sample/thinking_budget_state.py. This manipulation causes algorithmic complexity. This vulnerability is handled as CVE-2026-92365. The attack can be initiated remotely. There is not any exploit available. The pull request to fix this issue awaits acceptance.

Detailsinfo

A vulnerability classified as problematic was found in vllm-project vllm up to 0.29.0. Affected by this vulnerability is an unknown code of the file vllm/v1/sample/thinking_budget_state.py. The manipulation with an unknown input leads to a algorithmic complexity vulnerability. The CWE definition for the vulnerability is CWE-407. An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached. As an impact it is known to affect availability.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-92365. The exploitation appears to be easy. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

The pull request to fix this issue awaits acceptance.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Project Management Software

Vendor

• vllm-project

Name

• vllm

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6
• 0.7
• 0.8
• 0.9
• 0.10
• 0.11
• 0.12
• 0.13
• 0.14
• 0.15
• 0.16
• 0.17
• 0.18
• 0.19
• 0.20
• 0.21
• 0.22
• 0.23
• 0.24
• 0.25
• 0.26
• 0.27
• 0.28
• 0.29.0

Website

• Product: https://github.com/vllm-project/vllm/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Submitinfo

Accepted

• Submit #935016: vLLM Project vLLM >=0.26.0 Inefficient Algorithmic Complexity (by JPengLi)

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion