Vulnerability · CVE-2026-115917
vLLM: Permissive default CORS origins allow cross-origin requests to the vLLM HTTP server
Published Oct 26, 2026 · catalog updated Oct 31, 2026 · vLLM: Permissive default CORS
Last checked Nov 1, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-115917. EPSS is 0.24%. Act only if a listed version of vLLM: Permissive default CORS is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (vLLM: Permissive default CORS).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-100653 · High
- CVE-2026-44223 · Medium
- CVE-2026-44222 · High
- CVE-2026-7141 · Low
- CVE-2026-34756 · Medium
- Severity
- Medium4.7
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.24%
- Remediation
- Version ranges on file
- Affected products
- PyPI vllm · cpe vllm/vllm · pip vllm
### Summary The OpenAI-compatible server registers Starlette with defaulting to , and performs no authentication unless (or ) is configured. A web page on any origin can send requests to a vLLM server that the victim's browser can reach (for example or an internal/VPN address) and read the responses. The default blocks cookie-bearing cross-origin requests; because vLLM authenticates with a bearer header rather than cookies, the wildcard still permits untokenized access to an unauthenticated server and read access when the caller already holds a token. ### Details Affected components - - default value. - - registration. - - auth middleware and its guarded path prefixes. Root cause : : The auth middleware is added only when a token is configured and guards only the , , , and prefixes. and are inside and therefore do require a key when one is set; they are open only when no key is configured and dynamic LoRA updating is enabled. ### Impact - A malicious page can enumerate models ( ), issue , consume GPU time, and read model output through the victim's browser. - When the server is reachable only from the victim's network, the browser acts as a proxy a remote website could not otherwise use. - With , cookie-based CSRF does not apply; the exposure is cross-origin request execution and response disclosure. This advisory was fixed in [MR61009](https://github.com/vllm-project/vllm/pull/61009).
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- PyPI vllm0 → 0.32.0
- cpe vllm/vllm< 0.32.0
- pip vllm< 0.32.0
How to fix CVE-2026-115917
Upgrade
CVE-2026-115917 lists a fix boundary at 0.32.0. Compare the installed build with that boundary before you change production.
Version check
Affected < 0.32.0
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-115917. EPSS is 0.24%. Act only if a listed version of vLLM: Permissive default CORS is installed.
Which versions are affected?
Compare what you have installed with 0 → 0.32.0, < 0.32.0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-346; CWE-942: Permissive Cross-domain Policy with Untrusted Domains. EPSS 0.24%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 26, 2026 · Red Hat Security Data
Detected
vllm: vLLM: Information disclosure via permissive CORS configuration
Oct 28, 2026 · GitHub Advisory Database
Fix available
vllm fixed in 0.32.0
Oct 28, 2026 · GitHub Advisory Database
Fix available
vllm fixed in 0.32.0
Oct 28, 2026 · GitHub Advisory Database
Updated
### Summary The OpenAI-compatible server registers Starlette with defaulting to , and performs no authentication unless (or ) is configured. A web page on any origin can send requests to a vLLM server that the victim's browser can reach (for example or an internal/VPN address) and read the responses. The default blocks cookie-bearing cross-origin requests; because vLLM authenticates with a bearer
Oct 31, 2026 · NIST NVD
Updated
vLLM is an inference and serving engine for large language models. Prior to 0.32.0, the OpenAI-compatible server configures Starlette CORSMiddleware with allowed_origins set to a wildcard by default. A malicious web page can use a victim's browser to reach an unauthenticated vLLM server on localhost, an internal network, or a VPN, call endpoints including GET /v1/models and POST /v1/chat/completio
Sources
- CVE.orgVulnerability recordCVE-2026-115917
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-115917
30-day exploitation probability 0.24%
first.org - GitHub Advisory DatabasePackage advisoryGHSA-vvpg-rrww-wpmh
vLLM: Permissive default CORS origins allow cross-origin requests to the vLLM HTTP server
github.com - NIST NVDVulnerability recordCVE-2026-115917
vLLM is an inference and serving engine for large language models. Prior to 0.32.0, the OpenAI-compatible server configures Starlette CORSMiddleware with allowed_origins set to a wildcard by default. A malicious web page can use a victim's browser to reach an unauthenticated vLLM
nvd.nist.gov - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-vvpg-rrww-wpmh
vLLM: Permissive default CORS origins allow cross-origin requests to the vLLM HTTP server
osv.dev - Red Hat Security DataVendor advisoryCVE-2026-115917
vllm: vLLM: Information disclosure via permissive CORS configuration
access.redhat.com
References
Freshness
Last verified in this catalog Nov 1, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 1, 2026
- NIST NVDOct 31, 2026
- GitHub Advisory DatabaseOct 30, 2026
- OpenSSF OSV / OSV ScannerOct 29, 2026
- CVE.orgOct 27, 2026
- Red Hat Security DataOct 27, 2026