Evidence · DiggingBeagle record
vLLM PIL image error path discloses process object address
Researcher advisory for uppercase hexadecimal PIL __repr__ bypass of vLLM error sanitizer.
- Published
- Nov 13, 2026
- Source role
- primary disclosure
Evidence record
Researcher advisory for uppercase hexadecimal PIL __repr__ bypass of vLLM error sanitizer.
Claim-level citations (2)
- supportsA 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. 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.
vLLM GHSA-m9fg-w9qh-67pc, scrubber pattern vs PIL __repr__ and endpoint reproduction
- supportsA real PIL image exception bypassed a sanitizer whose regression test used an unrealistically lowercase example: 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.
Primary disclosure: results, scope and limitations