CVE-2026-9540: vllm-project vllm OpenAI-compatible Serving Path denial of service
A vulnerability was identified in vllm-project vllm 0.19.0. This issue affects some unknown processing of the component OpenAI-compatible Serving Path. Such manipulation leads to denial of service. It is possible to launch the attack remotely. The exploit is publicly available and might be used. The pull request to fix this issue awaits acceptance.
CVE-2026-9540 is a remotely reachable denial-of-service issue in vllm-project vLLM 0.19.0’s OpenAI-compatible serving path. A successful attack can disrupt model-serving availability. The sources say a public exploit exists and a fix pull request is pending, but they do not show confirmed active exploitation.
Executive priority
Prioritize if vLLM supports customer-facing or business-critical AI services. The issue appears availability-focused rather than data theft, but public exploit availability and pending fix status increase operational urgency for exposed deployments.
Technical view
The issue is reported as CWE-404 in unknown processing of the OpenAI-compatible Serving Path. CVSS v4.0 is 6.9 with network attack vector, low complexity, no privileges, no user interaction, and low availability impact. The fix is referenced as GitHub PR 37594, awaiting acceptance in the source bundle.
Likely exposure
Exposure is most likely where vLLM 0.19.0 is deployed with its OpenAI-compatible API reachable by untrusted users or the internet. Internal-only deployments still carry risk if many tenants, services, or users can send requests to the serving path.
Exploitation context
The bundle states the exploit is public and might be used. CISA KEV status is false, and the provided sources do not confirm active exploitation in the wild. Treat this as credible public-risk DoS exposure, not a confirmed campaign.
Researcher notes
Evidence is limited to public advisory metadata, issue tracking, and a pending pull request. The affected component is named, but root cause details and final patched version are not established in the provided bundle. Avoid assuming broader version impact beyond vLLM 0.19.0.
Mitigation direction
Inventory all vLLM deployments and identify version 0.19.0.
Restrict OpenAI-compatible API access to trusted networks or authenticated clients.
Apply gateway rate limits and resource controls where already available.
Monitor GitHub PR 37594 and vendor guidance for an accepted fix.
Deploy the vendor-approved fix or upgrade path when available.
Validation and detection
Confirm package, image, or deployment manifests for vLLM 0.19.0.
Map which OpenAI-compatible endpoints are reachable from untrusted networks.
Review logs and metrics for request spikes or availability degradation.
Track GitHub issue 37343 and PR 37594 for status changes.
Use only vendor-safe, non-production validation guidance.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-404: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve
time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present,
the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-404 · source CWE mapping
Improper Resource Shutdown or Release
Improper Resource Shutdown or Release represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.