CVE•Published 2026-10-05•Modified 2026-10-08•0 articles on news•4 live references•NVD data

CVE-2026-105752Vllm · Vllm

Vulnerability data via NVD (ingested)

CVSS v3.1
3.1
LOW
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS percentile
11
Exploit Prediction Scoring System · top 89% of all CVEs
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
Published 2026-10-05
Modified 2026-10-08

External references

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).

More intel sources (5)

Known PoCs on GitHub

No public proof-of-concept repositories found for CVE-2026-105752 on GitHub.
We haven't classified any articles referencing CVE-2026-105752 yet. The external references above still apply.