vLLM removes many in-memory object-address strings from errors before returning them to a client. The sanitizer pattern only matched lowercase hexadecimal characters, while PIL Image.repr emits addresses in uppercase and can be interpolated into a processor exception. The researcher supplied an image that triggered the error path and returned a live heap…
Inspect the ClaimsCase · DiggingBeagle record
A real PIL image exception bypassed a sanitizer whose regression test used an unrealistically lowercase example
vLLM removes many in-memory object-address strings from errors before returning them to a client. The sanitizer pattern only matched lowercase hexadecimal characters, while PIL Image.__repr__ emits addresses in uppercase and can be interpolated into a processor exception.
Public disclosure: Nov 13, 2026
A user-supplied image reaches a vulnerable model frontend error handler.
At a glance
An image object is included in an exception and the sanitizer misses PIL's uppercase hexadecimal address formatting.
Read the implicationsThe evidence is bounded by the cited source and test setting. Broader incidence, other environments, and actual production consequences are not established merely by these observations.
Limits and uncertaintyFull account
vLLM removes many in-memory object-address strings from errors before returning them to a client. The sanitizer pattern only matched lowercase hexadecimal characters, while PIL Image.repr emits addresses in uppercase and can be interpolated into a processor exception.
The researcher supplied an image that triggered the error path and returned a live heap pointer. A later fix covers the real uppercase form. This matters as an information disclosure in a model-serving API, not a demonstrated arbitrary memory read or code execution.
Exposure requires that the affected image-processing error path be reachable by the caller. A configured API key may not protect every convenience endpoint in a deployment, so route-level policy must be inspected separately.
The evidence is bounded by the cited source and test setting. Broader incidence, other environments, and actual production consequences are not established merely by these observations.
Mechanism and trust boundary
- 01
Starting condition
A user-supplied image reaches a vulnerable model frontend error handler.
Boundary: precondition and attacker capability
- 02
Trust boundary crossed or evaluated
The researcher supplied an image that triggered the error path and returned a live heap pointer. A later fix covers the real uppercase form. This matters as an information disclosure in a model-serving API, not a demonstrated arbitrary memory read or code execution.
Boundary: mechanism
- 03
Observed consequence
An image object is included in an exception and the sanitizer misses PIL's uppercase hexadecimal address formatting.
Boundary: observed effect and limitations
Claims & evidence
CLM-NOV15-VLLMPTR-MECHvLLM removes many in-memory object-address strings from errors before returning them to a client. The sanitizer pattern only matched lowercase hexadecimal characters, while PIL Image.__repr__ emits addresses in uppercase and can be interpolated into a processor exception. The researcher supplied an image that triggered the error path and returned a live heap pointer. A later fix covers the real uppercase form. This matters as an information disclosure in a model-serving API, not a demonstrated arbitrary memory read or code execution.supported
Basis: reported finding
- supportsvLLM PIL image error path discloses process object addressprimary disclosure
vLLM GHSA-m9fg-w9qh-67pc, scrubber pattern vs PIL __repr__ and endpoint reproduction
CLM-NOV15-VLLMPTR-SCOPEExposure requires that the affected image-processing error path be reachable by the caller. A configured API key may not protect every convenience endpoint in a deployment, so route-level policy must be inspected separately. The evidence is bounded by the cited source and test setting. Broader incidence, other environments, and actual production consequences are not established merely by these observations.supported
Basis: reported finding
- supportsvLLM PIL image error path discloses process object addressprimary disclosure
Primary disclosure: results, scope and limitations
Implications
An image object is included in an exception and the sanitizer misses PIL's uppercase hexadecimal address formatting.
Controls and mitigations
- Apply a fixed serving version and test sanitization using actual library objects, not only hand-constructed test literals.
- Audit authentication for /tokenize and related media paths independently of chat completion authorization.
Unknowns and contradictions
- The evidence is bounded by the cited source and test setting. Broader incidence, other environments, and actual production consequences are not established merely by these observations.
Sources and citation
Material revision history
- Nov 15, 2026 · Canonical change recorded · new in release · revision 250