CVE-2026-126395
Awaiting Analysis Awaiting Analysis - Queue

Information Disclosure in vLLM via PIL Image Address Leak

Vulnerability report for CVE-2026-126395, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-13

Last updated on: 2026-11-13

Assigner: VulnCheck

Description

vLLM from 0.14.0rc1 before 0.31.0 contains an information disclosure vulnerability in sanitize_message() whose lowercase-only regex fails to scrub uppercase PIL image addresses. Unauthenticated attackers can send a crafted PNG to endpoints such as /tokenize, triggering HF-processor errors that leak live server heap addresses useful for ASLR bypass.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-13
Last Modified
2026-11-13
Generated
2026-11-13
AI Q&A
2026-11-13
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
vllm vllm From 0.14.0rc1 (inc) to 0.31.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-532 The product writes sensitive information to a log file.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

vLLM versions 0.14.0rc1 through 0.31.0 have a flaw in the sanitize_message() function. The function uses a regex that only matches lowercase hexadecimal addresses, but PIL image addresses use uppercase. Attackers can send a crafted PNG to endpoints like /tokenize, causing errors that leak live server heap addresses. This helps bypass ASLR protections.

Detection Guidance

To detect this vulnerability, inspect vLLM versions between 0.14.0rc1 and 0.31.0. Check if the sanitize_message() function uses a case-sensitive regex pattern like r" at 0x[0-9a-f]+" without handling uppercase hex addresses. Review error logs for endpoints like /tokenize that may leak heap addresses in uppercase format (e.g., 0x{id(self):X}).

Commands to check: grep -r "sanitize_message" /path/to/vllm/; grep -r "0x[0-9A-F]" /var/log/vllm/ or application logs. Monitor for PIL-related errors in Hugging Face processor logs.

Impact Analysis

Unauthenticated attackers could exploit this to obtain heap memory addresses from your vLLM server. This information could be used for further attacks like ASLR bypass, potentially leading to remote code execution or other malicious activities.

Compliance Impact

This vulnerability may lead to unauthorized information disclosure, violating data protection principles in GDPR and HIPAA. It could result in non-compliance due to potential exposure of sensitive server memory details, though specific regulatory impacts depend on deployment context.

Mitigation Strategies

Immediately upgrade vLLM to version 0.31.0 or later. Update the sanitize_message() function regex to include uppercase hex characters (e.g., [0-9a-fA-F]) and add re.IGNORECASE flag. Disable unauthenticated endpoints like /tokenize if not required.

Apply input validation for PNG uploads to prevent crafted files. Review and sanitize all error messages to avoid leaking heap addresses. Monitor logs for suspicious requests targeting multimodal endpoints.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-126395. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...