NewApp Monitoring is liveSign up free
AgentbeamBeta
AI agent vulnerability · vLLM

CVE-2026-115915: vLLM: Untrusted EPS inputs can trigger denial of service or Ghostscript RCE

highCVSS 3.1 8.1GHSA-h3rc-j82p-2c3h

vLLM before 0.32.0 opens untrusted image bytes with Pillow format autodetection and no allowlist, so an EPS payload labeled `image/png` can reach the host's Ghostscript. On a host with a Ghostscript build affected by CVE-2024-29510, that gives command execution as the vLLM user. Older Pillow (12.0.0 to 12.2.0) adds a hang-based denial of service. Upgrade to vLLM 0.32.0.

Published Oct 28, 2026 · Analysis Oct 29, 2026

What an attacker can do

ImageMediaIO passes request image bytes to Image.open(BytesIO(data)). The MIME label in a data URL does not choose the decoder. Pillow identifies EPS by its signature, and image.load() then runs Ghostscript with -dSAFER, -sDEVICE=pnmraw and the attacker's file. CVE-2024-29510 lets crafted PostScript bypass -dSAFER, so the attacker's commands run with the vLLM process's privileges. The advisory claims no new Ghostscript flaw. Ghostscript is not a vLLM dependency, so this needs a vulnerable Ghostscript on the host or in the image. The reporter used Debian Ghostscript 10.03.0 and Pillow 12.3.0 with the vllm==0.30.0 wheel. A marker touch command ran through ImageMediaIO.load_base64(). The HTTP path (parse_image(), fetch_image(), the media connector) was traced in source but not run end to end.

The same boundary has a second problem. With Pillow 12.0.0 to 12.2.0, CVE-2026-59203 makes the EPS parser loop on a negative %%BeginBinary count. In a local check, eight concurrent loads filled the connector's eight media-loading threads and queued a benign load behind them. That path gives no code execution.

The attacker needs a request path that accepts images and the ability to reach it under your authentication policy. The CVSS vector shows no privileges required, so an open endpoint is the worst case.

Who is affected

The advisory tested only PyPI vllm==0.30.0. The package data lists all versions below 0.32.0 as vulnerable. The RCE chain also needs a Ghostscript executable affected by CVE-2024-29510 (fixed upstream in 10.03.1). The denial of service needs Pillow 12.0.0 to 12.2.0. vLLM 0.30.0 leaves Pillow unpinned, so an old environment can keep a bad Pillow.

pip show vllm pillow
gs --version

Also check your container images, since Ghostscript often arrives as an OS package.

vllm

Ecosystem
PyPI
Affected
< 0.32.0
Fixed in
0.32.0
Check
pip show vllm

How to fix it

Upgrade to vLLM 0.32.0:

pip install --upgrade "vllm>=0.32.0"

The fix (pull request 60022) adds a Pillow format allowlist and an open_image() helper that ImageMediaIO.load_bytes() now uses. It excludes EPS and other formats that call external renderers. The PR names no workaround. As defense in depth, update Ghostscript to 10.03.1 or later, or remove it from the serving image, and keep Pillow at 12.3.0 or later. Limit who can reach image-capable routes.

How to tell if you were hit

Look for chat requests whose image data URL declares image/png or another raster type but whose decoded bytes start with %!PS or an EPS header (%!PS-Adobe). Check for Ghostscript (gs) child processes under the vLLM server, and for files or shells spawned by that user. For the denial of service, watch for image requests that never finish and for media-loading threads stuck in Pillow's EPS parser. Rejected EPS inputs after the upgrade are expected.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Summary

In vLLM 0.30.0, ImageMediaIO passes attacker-controlled image bytes to Pillow's format autodetection without restricting the accepted formats; the request's MIME label does not constrain decoder selection. An EPS payload labeled image/png reached the host's Ghostscript executable. On a host with Ghostscript affected by CVE-2024-29510, this exposes the known Ghostscript sandbox escape through vLLM's image-loading path and can execute commands with the vLLM process's privileges. A bounded marker-command payload executed through the PyPI wheel's actual ImageMediaIO.load_base64() implementation using Debian Ghostscript 10.03.0. The loader-level execution is reproduced; the HTTP request path is source-traced but was not exercised end to end. This report concerns vLLM's untrusted-format dispatch and does not claim a new Ghostscript vulnerability. Exploitation requires an image-capable request path, a caller able to reach it under the deployment's authentication policy, and a vulnerable host Ghostscript build.

Details

ImageMediaIO is the boundary where attacker-controlled bytes enter Pillow's format autodetection: the declared MIME type does not constrain decoder selection, and the loader calls Image.open(BytesIO(data)) without a Pillow format allowlist. Pillow recognizes EPS by its file signature, and vLLM's subsequent image.load() call enters Pillow's EPS processing path. The OpenAI chat multimodal parser reaches this path through `parse_image()` and `fetch_image()` and the media connector; the data URL path extracts the MIME label and forwards the bytes to the loader (source). This is the vLLM-specific issue: untrusted image bytes can select a Pillow-supported format parser. Each downstream impact depends on the relevant parser, component version, and host configuration.

Pillow recognizes EPS by its file signature and invokes Ghostscript with -dSAFER, -sDEVICE=pnmraw, and the untrusted EPS input (Pillow EPS plugin, load path). The command execution in this report uses the already-known Ghostscript CVE-2024-29510, which allows crafted PostScript to bypass -dSAFER; Ghostscript lists 10.03.1 as the upstream fixed version (Ghostscript CVE details). This is an N-day dependency chain: CVE-2024-29510 provides the command-execution primitive, while the vLLM-specific issue is that untrusted, remotely supplied image bytes can reach the affected interpreter. No new Ghostscript flaw is claimed here.

The vLLM Python requirements declare Pillow but not Ghostscript, so this execution chain depends on a Ghostscript executable supplied by the host or deployment image. I reproduced command execution with the PyPI vllm==0.30.0 wheel, Pillow 12.3.0, and Debian amd64 Ghostscript 10.03.0~dfsg-1. The Codean Labs CVE-2024-29510 testkit identified that Ghostscript build as vulnerable. The adapted EPS payload ran only touch on a temporary marker. The marker existed after the loader call, although Pillow then raised ValueError because the exploit changes Ghostscript's output device. The API route was traced in source but a model-backed HTTP request was not run. Only PyPI vllm==0.30.0 was checked; no wider affected release range or other Ghostscript vendor build is claimed.

The same input boundary also exposes a separate Pillow-only denial-of-service condition when the installed Pillow version is 12.0.0–12.2.0. CVE-2026-59203 is triggered by a negative %%BeginBinary byte count and causes Pillow's EPS parser to loop during Image.open(); it does not invoke Ghostscript or provide code execution (Pillow advisory). The published `vllm==0.30.0` requirements leave Pillow unpinned, so an existing environment can retain an affected Pillow version; the source at commit bc21cba9673cfc2256a2726b4bc32f062237cd35 requires `pillow>=12.3.0`. In an isolated local check with Pillow 12.2.0, the official sample hung through ImageMediaIO.load_bytes() and MediaConnector.fetch_image_async(). Eight concurrent image loads occupied the connector's eight media-loading threads and left a benign image load queued. Pillow 12.3.0 rejected the sample promptly. This confirms a conditional media-processing DoS path, separate from the Ghostscript RCE chain; full HTTP-server availability was not measured.

Impact

When a vLLM image-processing endpoint accepts attacker-supplied content and the host has Ghostscript affected by CVE-2024-29510, a caller who can reach the endpoint can trigger command execution as the vLLM process user. API-key authentication and network access controls determine who can reach the request path. Deployments without Ghostscript or with a build fixed for CVE-2024-29510 are not affected by this execution chain. Separately, existing environments that run vLLM 0.30.0 with Pillow 12.0.0–12.2.0 are exposed to CVE-2026-59203 through the same image-format dispatch boundary; the demonstrated impact is exhaustion of media-loading workers, and this Pillow CVE does not cause RCE. The report asks vLLM to assess and address the unsafe dispatch of untrusted image bytes and the affected dependency combinations.

This advisory was fixed in MR60022.

Credited to LittlehamsterXu, jperezdealgaba.

Questions

Am I exposed if Ghostscript is not installed?

You are not exposed to the code-execution chain, which needs a Ghostscript build affected by CVE-2024-29510. You may still hit the Pillow hang if you run Pillow 12.0.0 to 12.2.0, until you upgrade vLLM to 0.32.0.

Does the declared image MIME type protect me?

No. The data URL's MIME label does not constrain decoder choice. An EPS payload labeled image/png still reached Ghostscript in the reporter's test.

Has the HTTP exploit path been proven?

Not end to end. Command execution was shown through the loader (ImageMediaIO.load_base64()). The API route was traced in source but a model-backed HTTP request was not run.

Is it exploited in the wild?

No source says so, and it is not in CISA's KEV catalog.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

Coverage on the Beam blog

More vLLM vulnerabilities

All vLLM entries