Skip to main content
Menu
CVEs

CVE

vLLM heap address disclosure in sanitize_message()

CVE-2026-126395EUVD-2026-125170GHSA-8HQR-48H6-R93JGHSA-M9FG-W9QH-67PCPublished Updated

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 0.31.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 0.31.0.

Summary

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.

cve.now Index

39cve.now Index 39 of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach12/20vllm: 578.2K downloads a week
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 84 if added to CISA KEV
  • Would score about 79 if CISA's SSVC rates exploitation active
  • Would score about 44 if advisories confirm default setups are exposed

Impact

  • Widely used

    vllm has 578.2k weekly downloads.Source: pypistats.org

    93 packages depend on vllm.Source: deps.dev

What to do

  • Upgrade to a fixed version: 0.31.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126395 (vLLM 0.14.0rc1 before 0.31.0 Heap Address Disclosure via sanitize_message()), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126395 (entry last updated 2026-11-13):
Affected:
- PyPI package vllm: from 0.14.0rc1, fixed in 0.31.0
Fixed versions: 0.31.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126395 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126395 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/vllm-project/vllm/security/advisories/GHSA-m9fg-w9qh-67pc
- https://www.vulncheck.com/advisories/vllm-0.14-0rc1-before-0.31.0-heap-address-disclosure-via-sanitize-message
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126395
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126395"}.

Public exploit activity

100%0Nov 13Nov 19
  • EPSS: 0.35%

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • vllmPyPI

    From 0.14.0rc1 · fixed in 0.31.0

    Fixed in 0.31.0 (released Oct 5, 2026, 39 days before disclosure).

    The latest release, 0.33.0, is not affected.

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · vllm-project/vllm · Advisory GHSA-m9fg-w9qh-67pc
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-126395
RecordNVD · CVE-2026-126395
Other links 1
Linkvulncheck.com · advisories/vllm-0.14-0rc1-before-0.31.0-heap-address-disclosure-via-sanitize-message

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-126395

Is CVE-2026-126395 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-126395?

vllm (PyPI): from 0.14.0rc1 before 0.31.0.Source: cve.now feed data

How do I fix CVE-2026-126395?

Upgrade to a fixed version: 0.31.0.Source: cve.now feed data

More CVEs