Servers and applications
CVE-2026-105752
Harmony tool continuations drop `cache_salt` — restoring a cross-tenant prefix-cache membership oracle
- Severity
- Low 3.1
- Published
- 28 Sept 2026
- Last changed
- 8 Oct 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 0.30.0
- Exploit chance
- 0.2% in the next 30 daysHigher than 12% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Only under certain conditions · Needs a user account · No user action needed
- Attacker can
- Change some data
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N- Also known as
- GHSA-935w-9g4m-p28p
- Sources
- NVD, CVE Program, Project advisories (GitHub)
Description
On the GPT-OSS "Harmony" path (POST /v1/responses), a request that uses a built-in or MCP tool runs as a multi-turn loop: after each tool call vLLM re-renders the full next-turn Harmony prompt and re-submits it to the engine. Turn 1 correctly carries request.cache_salt, but the tool-continuation re-submission rebuilds the engine input via tokens_input(token_ids) with no cache_salt. The continuation prefix is therefore cached in the global unsalted namespace even though the caller opted into salting. A second tenant who can guess the low-entropy post-tool history submits the reconstructed continuation (unsalted) and reads exact per-turn cached-token counts from the Responses usage — restoring the prompt-membership oracle that cache_salt is documented to prevent.
Silently dropping a preserved salt after the supported tool workflow is enabled is a broken isolation control: the caller enabled salting and every turn should stay isolated, but continuation turns leak into the shared cache.
Affected software
| Software | Affected versions |
|---|---|
vLLMServers and applications · cna:vllm-project|vllm |
|
vLLMServers and applications · cpe:a:vllm:vllm |
|
vLLMServers and applications · github:vllm-project/vllm |
|
About vLLM
open-source software for large language model inference
- Docker Hub pulls
- 44,195,225Docker Hub, 15 Nov 2026
- GitHub stars
- 96,943GitHub, 15 Nov 2026
- Forks
- 24,836GitHub, 15 Nov 2026
- Latest release
- v0.33.0rc3GitHub, 15 Nov 2026
- Released
- 2 Nov 2026GitHub
- License
- Apache Software License 2.0Wikidata
- First published on GitHub
- 9 Feb 2023GitHub
Website Source code Docker image
Vulnerabilities in vLLM
- In our list
- 169
- Published in the last 12 months
- 150
- Critical, last 12 months
- 6
- High, last 12 months
- 63
- Known exploited
- 0
- CVE-2026-130686vLLM 0.6.0 before 0.33.0 Resource Exhaustion via Multi-Image RequestsHigh 8.7 18 Nov 2026
- CVE-2026-130684vLLM before 0.33.0 Path Traversal via speculators_config verifier.name_or_pathMedium 5.3 18 Nov 2026
- CVE-2026-130685vLLM 0.28.0 before 0.33.0 Unauthenticated DoS via Out-of-Range Prompt Token IDHigh 8.7 18 Nov 2026
- GHSA-xgh8-qwjh-q853/v1/systemone bypasses the --trust-request-chat-template gateMedium 6.5 18 Nov 2026
- CVE-2026-129356vllm-project vllm Common Prefix single_type_kv_cache_manager.py race conditionLow 2.3 15 Nov 2026
- CVE-2026-126394vLLM 0.30.0 before 0.31.0 Resource Exhaustion via OpenPangu Video Backend num_framesMedium 6.9 13 Nov 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-105752
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-105752
- GitHub Advisory Database https://github.com/advisories/GHSA-935w-9g4m-p28p
- github.com https://github.com/vllm-project/vllm/security/advisories/GHSA-935w-9g4m-p28p