> ## Content Index
> Fetch the complete content index at: https://ping2prompt.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# vLLM 0.33.0 fixes image-URL resource exhaustion and a model redirect flaw
- URL: https://ping2prompt.com/vllm-0-33-0-image-url-resource-exhaustion-model-redirect-flaw/
- Published: 2026-11-18T14:41:48.000Z
- Updated: 2026-11-18T17:21:27.000Z
- Description: vLLM before 0.33.0 has a high-severity flaw, CVE-2026-130686 (8.7), letting remote clients exhaust frontend resources with many image URLs, plus CVE-2026-130684, a model-publisher redirect leaking tokenizer data. Upgrade to vLLM 0.33.0 or later.
- Author: Ping2Prompt Newsroom
- Tags: vLLM, AI, Vulnerabilities, High, #short-ping

## vLLM 0.33.0 closes a high-severity image-URL flood

vLLM before 0.33.0 has no request-wide media budget, which lets a remote inference client exhaust resources on the frontend. The flaw is CVE-2026-130686, scored 8.7 (high) under CVSS 4.0.

The attacker sends one compact request to `/v1/messages` or `/v1/responses` that contains many remote image URLs. The CVSS vector lists no privileges and no user interaction, and the impact is on availability.

vLLM downloads and decodes every image before it checks prompt length, so memory, CPU and connections on the frontend can run out.

## A second flaw lets a model publisher redirect the tokenizer

The release also covers a medium-severity flaw:

- **CVE-2026-130684 (medium, 5.3)**: a malicious model publisher sets `speculators_config` `verifier.name_or_path` in `config.json` to point at another local checkpoint directory, leaking its tokenizer vocabulary and giving query access to private models.

The leak is read through unauthenticated requests to the `/detokenize` endpoint.

## Which vLLM versions and setups are exposed

CVE-2026-130686 affects vLLM from 0.6.0 up to, but not including, 0.33.0\. CVE-2026-130684 affects every vLLM version before 0.33.0.

Check your running version first. Then check whether untrusted clients can reach `/v1/messages` or `/v1/responses`, since that is where the image flood arrives. For the redirect flaw, look at where your model files come from, because the attacker is the model publisher editing `config.json`.

Treat both flaws as live risks without waiting for word on exploitation status.

## Upgrade vLLM to 0.33.0 or later

According to both CVE records, the affected range is "before 0.33.0", so update to vLLM 0.33.0 or later. Put the image-URL flaw first if your API is reachable by people you do not control.

## What the vLLM records leave unstated

The records name 0.33.0 only through the affected range and do not state a fix outright. NVD lists both entries as awaiting analysis and points to the advisories GHSA-5r3c-5x4v-8gjh and GHSA-qrj2-j723-m6w8.

| Product                | Affected                           | Fixed  |
| ---------------------- | ---------------------------------- | ------ |
| vLLM (CVE-2026-130686) | 0.6.0 up to, not including, 0.33.0 | 0.33.0 |
| vLLM (CVE-2026-130684) | before 0.33.0                      | 0.33.0 |

## Sources

- [nvd.nist.gov/vuln/detail/CVE-2026-130686](https://nvd.nist.gov/vuln/detail/CVE-2026-130686?ref=ping2prompt.com)
- [nvd.nist.gov/vuln/detail/CVE-2026-130684](https://nvd.nist.gov/vuln/detail/CVE-2026-130684?ref=ping2prompt.com)

---

This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our [editorial methodology](https://ping2prompt.com/about-how-we-work/) and the [corrections log](https://ping2prompt.com/corrections/). Spotted an error? Email [editor@ping2prompt.com](mailto:editor@ping2prompt.com).