GPU VulnDB

Database/AI/ML frameworks & serving

vLLM: error messages leak live server heap addresses to unauthenticated clients

CVSS 6.9CVE-2026-126395AI/ML frameworks & servingcurated

Impact

The regex in sanitize_message() only scrubs lowercase PIL image addresses, so uppercase ones get through. A crafted PNG sent to endpoints such as /tokenize makes the HF processor fail, and the error returned to the client contains live heap addresses from the serving process. The leak alone gives no code execution or data access. What it does give is an ASLR bypass, which makes any separate memory-corruption bug in the same vLLM process easier to exploit. That matters most on inference endpoints exposed to many tenants or to the internet.

Who can reach it

Anyone who can reach the vLLM HTTP API, for example /tokenize. No authentication is needed if the deployment does not enforce any. The model must accept image input.

What to do

Upgrade vLLM to 0.31.0 or later, which affects 0.14.0rc1 through 0.30.x, and restart the serving process. That means rolling each inference replica, which drops in-flight requests and reloads model weights. Until then, put authentication in front of the API and avoid sending raw processor errors back to untrusted clients.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.