GPU VulnDB

Database/AI/ML frameworks & serving

vLLM: Nemotron-VL processors disable the Pillow decompression-bomb guard, letting one image OOM the worker

CVSS 8.7CVE-2026-116177AI/ML frameworks & servingcurated

Impact

The Nemotron-VL processors set Pillow's Image.MAX_IMAGE_PIXELS to None globally, removing the decompression-bomb limit for the whole process. A single crafted image posted to /v1/chat/completions expands to arbitrary resident memory and the OOM killer takes the worker down. On a GPU node that means the model weights have to be reloaded into HBM, which costs minutes per restart, and in a shared endpoint every co-tenant on that worker loses service. Because the guard is disabled globally, non-Nemotron requests on the same process are affected too.

Who can reach it

Any unauthenticated client that can POST to the vLLM OpenAI-compatible endpoint. No credentials needed.

What to do

Upgrade vLLM to 0.25.0 or later and restart the serving workers (weights reload, so expect a cold start per replica). Where upgrade is not immediate, put a request-size and image-dimension limit in the proxy in front of vLLM and keep the endpoint off untrusted networks.

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.