CVSS 4.0
6.9 mediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NCVE-2026-126395 vLLM 0.14.0rc1 before 0.31.0 Heap Address Disclosure via sanitize_message()
Medium (6.9) in vllm-project vllm. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
On this page
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.
Severity
CVSS 3.1
5.3 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N- EPSS
- 0.4% estimated probability of exploitation activity in the next 30 days; 34th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-532 Insertion of Sensitive Information into Log File
- OWASP Top 10
- A09:2025 Logging & Alerting Failures
- Published
- Modified
- Assigned by
- VulnCheck (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-126395 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126395?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126395?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126395 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-126395)
HTML:
<a href="https://cve.bz/cve/CVE-2026-126395"><img src="https://cve.bz/cve/badge/CVE-2026-126395.svg" alt="CVE-2026-126395"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| vllm-project vllm | from 0.14.0rc1 before 0.31.0 |
Attack patterns (CAPEC)
- CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.