cve.bz

CVE-2026-105752 vllm vllm

3.1 lowEPSS 0.2%Fix available

Low (3.1) in vllm vllm. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in vllm 0.30.0.

On this page
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.

Severity

CVSS 3.1

3.1 low
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-524 Use of Cache Containing Sensitive Information
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-105752 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105752?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105752?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105752 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
vllm:vllmbefore 0.30.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-935w-9g4m-p28pPyPIvllm<0.30.00.30.0
PYSEC-2026-4308PyPIvllm<0.30.00.30.0

Red Hat

Red Hat rates this Low.

Red Hat's statement

A low severity flaw was found in vLLM, the LLM inference and serving engine shipped in Red Hat AI Inference Server 3 and Red Hat OpenShift AI (RHOAI). When a multi-turn request submitted through the /v1/responses endpoint uses a tool continuation, vLLM rebuilds the next-turn engine input without preserving the cache_salt value, so the continuation prefix is cached in the shared, unsalted namespace even when the caller enabled salting. On deployments with prefix caching enabled, which is the default, an authenticated tenant who can reconstruct another tenant's low-entropy post-tool history can submit the same continuation and use the per-turn cached-token counts reported in the response usage to determine whether that prefix was previously processed, defeating the tenant isolation that salted prefix caching is intended to provide. The resulting cross-tenant information disclosure is limited to confirming whether specific prompts or inputs were previously processed by another user; prompt content is not directly disclosed. Exploitation requires several specific preconditions, including an operator-enabled tool server, a victim request that sets cache_salt and triggers a tool continuation, and sufficiently accurate reconstruction of the victim's post-tool history. Both the Red Hat and upstream assessments rate this flaw Low severity (CVSS 3.1 score 3.1, CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N). Because this flaw is rated Low impact, the fix for the affected Red Hat AI Inference Server 3 and Red Hat OpenShift AI releases is deferred, as Red Hat does not file trackers for Low severity flaws; the residual risk is that an authenticated user of a multi-tenant deployment with prefix caching enabled could infer whether specific inputs of another tenant were processed.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. The upstream vLLM project has fixed this issue in version 0.30.0, but no fixed version is currently available for the affected Red Hat AI Inference Server 3 and Red Hat OpenShift AI releases because the fix is deferred for this Low severity flaw.

ProductPackageStateAdvisory
Red Hat AI Inference Serverrhaiis/vllm-cpu-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-cuda-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-neuron-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-rocm-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-spyre-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-tpu-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-cpu-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-cuda-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-gaudi-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-neuron-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-rocm-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-spyre-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-tpu-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-aws-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-azure-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-azure-rocm-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-gaudi-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-gcp-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-rocm-rhel9Fix deferred
7 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-105752.

Attack patterns (CAPEC)

  • CAPEC-204 Lifting Sensitive Data Embedded in Cache Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON