vllm-project · vLLM · published 2026-10-26
CVE-2026-115915vLLM: Untrusted EPS inputs can trigger denial of service or Ghostscript RCE
Routine No exploitation evidence; EPSS 0.7%.
CVE-2026-115915 is not known to be exploited in the wild. EPSS estimates a 0.7% chance of exploitation in the next 30 days, higher than 52% of all CVEs. This vLLM vulnerability: CVSS 8.1 (v3.1), a successful attack gives total control of the component. Fixed upstream in vLLM 0.32.0. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in vLLM 0.32.0.
Patch events
AI toolingvLLM
vLLM security release: 0.32.0
Upgrade to
0.32.0Why: Vendor security release for server software (most severe: CVE-2026-94624).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.7% (52th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.1 (v3.1)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- vllm-project vllm
< 0.32.0(affected)
Description (from the CVE record)#
vLLM is an inference and serving engine for large language models. Prior to 0.32.0, ImageMediaIO passes attacker-controlled image bytes to Pillow through Image.open(BytesIO(data)) without restricting decoder selection, and the MIME label does not constrain the selected format. Image-capable request paths through parse_image() and fetch_image() can therefore dispatch an EPS payload to host components. A host with Ghostscript affected by CVE-2024-29510 can execute commands with the vLLM process's privileges, while environments using Pillow 12.0.0 through 12.2.0 can trigger CVE-2026-59203 and exhaust media-loading workers. Deployments without the applicable vulnerable dependency are not affected by that corresponding impact. This issue is fixed in version 0.32.0.
Quoted from the CVE Program record.