CVE-2026-129356: vllm-project vllm Common Prefix single_type_kv_cache_manager.py race condition
Noroxi assessment
Priority: Monitor (action score 5/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.29% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: vllm-project vllm 0.32.0.
Low priority for now. Upgrade to vllm-project vllm 0.32.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A vulnerability was found in vllm-project vllm 0.30.0/0.31.0. This vulnerability affects unknown code of the file single_type_kv_cache_manager.py of the component Common Prefix Handler. The manipulation results in race condition. The attack may be performed from remote. Attacks of this nature are highly complex. It is stated that the exploitability is difficult. The exploit has been made public and could be used. Upgrading to version 0.32.0 is able to resolve this issue. The patch is identified as e687a251bb056fa527846633f7a1b0a6c0f42374. You should upgrade the affected component.
- Published
- Nov 15, 2026
- Updated
- Nov 16, 2026
- EPSS
- 0.2% · 22th percentile
- CWE
- CWE-362
Report tools
Action score
5
Low priority for now.
- CVSS
- 5 / 40 · 1.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulDB
- 2.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulDB). Independent of NVD's CPE analysis and usually ahead of it.
vllm-project vllm
- 0.32.0not affected
- 0.30.0, 0.31.0affected
Same product
vllm-project: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-9053Remote Code Execution in vllm-project/vllm39Monitor
- CVE-2026-126397vLLM 0.10.1 before 0.31.0 Cohere2 Vision DoS via max_patches34Monitor
- CVE-2026-126398vLLM 0.28.0 before 0.30.0 Denial of Service via Prompt Embeds on XD-RoPE Models32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-126395Nov 13, 2026 · vLLM 0.14.0rc1 before 0.31.0 Heap Address Disclosure via sanitize_message()27Monitor
- ← EarlierCVE-2026-126396Nov 13, 2026 · vLLM from 0.24.0 before 0.31.0 Resource Exhaustion via MiniMax M3 min_pixels27Monitor
- ← EarlierCVE-2026-126399Nov 13, 2026 · vLLM 0.19.0 before 0.31.0 Resource Exhaustion via Request-Level num_frames28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| vllm-project vllm | 0.32.0 · description | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 17, 2026+2 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Zyz3366 (VulDB User)reporter
Not on record for this CVE: variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → poc
- Exploit maturity— → none
- Fix✗ → ✓
- CVSS2.3 → 1.3
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- github.com/vllm-project/vllm/commit/e687a251bb056fa527846633f7a1b0a6c0f42374
- github.com/vllm-project/vllm/issues/61673
- github.com/vllm-project/vllm/pull/61126
- github.com/vllm-project/vllm/releases/tag/v0.32.0
- vuldb.com/cve/CVE-2026-129356
- vuldb.com/submit/1043823
- vuldb.com/vuln/437419
- vuldb.com/vuln/437419/cti
Vendor advisories and official records. Exploit/PoC links are deliberately left out.