CVE-2026-105752vLLM: Harmony tool continuations drop `cache_salt` — restoring a cross-tenant prefix-cache membership oracle
- 3.1LowCVSS base score
- 0.22%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
vLLM is an inference and serving engine for large language models. Prior to 0.30.0, Harmony tool continuations submitted through "POST /v1/responses" requests rebuild the next-turn engine input without preserving the cache_salt value, placing the continuation prefix in the global unsalted cache namespace even when the caller enabled salting. On deployments with prefix caching enabled, which is the default, an authenticated tenant who can reconstruct a victim's low-entropy post-tool history can submit the same continuation and use the cached_tokens_per_turn count to determine whether the prefix was previously processed, defeating the intended tenant isolation of salted prefix caching. This issue is fixed in version 0.30.0.
Timeline
ID reserved
By GitHub_M
Published
- 1 day later
· 1 day later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_MCNA (assigner) | 3.1 | Low3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N |
| NVDNVD · Analyzed | 3.1 | Low3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N |
- EPSS (exploitation in 30 days)
- 0.22% · top 88% of all CVEs (13 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Low 3.1.
Affected products
- affected < 0.30.0
Affected packages
From reviewed advisories of the GitHub Advisory Database.
References
References5
- https://github.com/vllm-project/vllm/security/advisories/GHSA-935w-9g4m-p28p (opens in a new tab)x_refsource_CONFIRM
- https://github.com/vllm-project/vllm/pull/50195 (opens in a new tab)x_refsource_MISC
- https://github.com/vllm-project/vllm/pull/51818 (opens in a new tab)x_refsource_MISC
- https://github.com/vllm-project/vllm/commit/6a2a2bb02b563b83f946012959fd3927984d072a (opens in a new tab)x_refsource_MISC
- https://github.com/vllm-project/vllm/releases/tag/v0.30.0 (opens in a new tab)x_refsource_MISC
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-92842 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisory GHSA-935w-9g4m-p28p (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-105752)Record last updated .