vllm-project vllm 0.30.0/0.31.0 Common Prefix single_type_kv_cache_manager.py race condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $0-$5k | 0.00+ |
Summary
A vulnerability has been found in vllm-project vllm 0.30.0/0.31.0 and classified as problematic. This issue affects some unknown processing of the file single_type_kv_cache_manager.py of the component Common Prefix Handler. This manipulation causes race condition. The identification of this vulnerability is CVE-2026-129356. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. The affected component should be upgraded.
Details
A vulnerability classified as problematic was found in vllm-project vllm 0.30.0/0.31.0. Affected by this vulnerability is an unknown part of the file single_type_kv_cache_manager.py of the component Common Prefix Handler. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. As an impact it is known to affect confidentiality, integrity, and availability.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-129356. The exploitation appears to be difficult. The attack can be launched remotely. Technical details and also a public exploit are known.
It is possible to download the exploit at github.com. It is declared as proof-of-concept.
Upgrading to version 0.32.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch e687a251bb056fa527846633f7a1b0a6c0f42374 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.5
VulDB Base Score: 5.0
VulDB Temp Score: 4.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: vllm 0.32.0
Patch: e687a251bb056fa527846633f7a1b0a6c0f42374
Timeline
11/14/2026 Advisory disclosed11/14/2026 VulDB entry created
11/14/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 61673
Status: Confirmed
Confirmation: 🔒
CNA: VulDB
CVE: CVE-2026-129356 (🔒)
GCVE (CVE): GCVE-0-2026-129356
GCVE (VulDB): GCVE-100-437419
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 11/14/2026 07:47Changes: 11/14/2026 07:47 (63)
Complete: 🔍
Submitter: Zyz3366
Cache ID: 216::103
Submit
Accepted
- Submit #1043823: vLLM Project vLLM v0.30.0, v0.31.0 Improper Resource Management (by Zyz3366)
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.