cve.bz

CVE-2026-105756 vllm vllm: Uncaught Exception

6.5 mediumEPSS 0.3%Fix available

Medium (6.5) in vllm vllm. EPSS 0.3% 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, OpenAI-compatible request models accept a non-empty cache_salt value without enforcing the character and length restrictions required by the IPCCacheServerKey consumer in LMCache-MP. On deployments using the LMCache-MP connector, a salt that contains a forbidden character or exceeds the permitted length can raise an uncaught ValueError during scheduler cache lookup, causing EngineCore to terminate and denying service to all concurrent users. This issue is fixed in version 0.30.0.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 27th 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-20 Improper Input Validation
CWE-248 Uncaught Exception
OWASP Top 10
A05:2025 Injection, A10:2025 Mishandling of Exceptional Conditions
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-105756 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105756?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105756?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-105756 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-2823-qmq8-rwvjPyPIvllm<0.30.00.30.0
PYSEC-2026-4306PyPIvllm<0.30.00.30.0

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate severity denial-of-service vulnerability was found in vLLM, as shipped in Red Hat AI Inference Server and Red Hat OpenShift AI (RHOAI). vLLM's OpenAI-compatible API endpoints accept a client-supplied cache_salt parameter that is validated only as a non-empty string, without character or length restrictions. On deployments where the LMCache-MP KV connector is enabled, the value is forwarded unvalidated into the scheduler's cache lookup, where the downstream LMCache library raises a ValueError for salts that contain forbidden characters (for example '@', '/', backslash, or NUL) or exceed 128 characters. Because this exception is not handled at the request level, the EngineCore process treats it as fatal and terminates, disrupting service for all concurrent users. An authenticated remote attacker with access to the inference API can trigger this crash with a single crafted request. The flaw affects availability only, with no impact on confidentiality or integrity (CVSS 3.1 score of 6.5, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), which matches the upstream severity rating. Because the impact is moderate and the CVSS score is below 7.0, the fix for the affected Red Hat AI Inference Server and Red Hat OpenShift AI components has been deferred. The residual risk is limited to a denial of service against a single vLLM serving instance by an already-authenticated API user, and only on deployments that use the LMCache-MP connector.

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.

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-105756.

Attack patterns (CAPEC)

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

References

Check your stackJSON