# CVE-2026-100649: vLLM before 0.29.0 Resource Limit Bypass via Sampler Subclass

> Unauthenticated attackers can bypass resource limits in vLLM to exhaust GPU memory, causing denial of service.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Sep 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-hf74-6fwg-ghj7, GHSA-j682-9xp5-rrf3, MINI-24pr-5qc2-rp4j, MINI-489v-gg54-9rhm, MINI-r3xf-6mv6-g7mr

## What is CVE-2026-100649?

CVE-2026-100649 is a medium-severity denial of service vulnerability in Vllm Vllm, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

vLLM before 0.29.0 contains a resource-limit bypass vulnerability in PyNvVideoCodec decoder allocation where sampler subclass shadowing allows independent counter increments. Unauthenticated attackers can select different sampler subclasses in video requests to exceed configured decoder limits and exhaust unaccounted GPU memory.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-100649?

It affects 1 product.


Products: Vllm Vllm.

## How do I fix CVE-2026-100649?

Upgrade to a fixed version.

## Is CVE-2026-100649 being exploited?

There is no known exploitation of CVE-2026-100649 in the wild and no public exploit code.

## Other vulnerabilities in Vllm Vllm

- [CVE-2025-32444](https://insights.sbomify.com/CVE-2025-32444/): vLLM Vulnerable to Remote Code Execution via Mooncake Integration (critical 10.0)
- [CVE-2026-22778](https://insights.sbomify.com/CVE-2026-22778/): vLLM leaks a heap address when PIL throws an error (critical 9.8)
- [CVE-2025-47277](https://insights.sbomify.com/CVE-2025-47277/): vLLM Allows Remote Code Execution via PyNcclPipe Communication Service (critical 9.8)
- [CVE-2024-11041](https://insights.sbomify.com/CVE-2024-11041/): Remote Code Execution in vllm-project/vllm (critical 9.8)
- [CVE-2026-48746](https://insights.sbomify.com/CVE-2026-48746/): vLLM: OpenAI auth bypass (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100649 and fix it if it is affected.

What it is: CVE-2026-100649 is a medium-severity denial of service vulnerability in Vllm Vllm, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100649 in the wild and no public exploit code.

Affected product: Vllm Vllm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100649/ (Markdown: https://insights.sbomify.com/CVE-2026-100649/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100649
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100649
- OSV: https://osv.dev/vulnerability/CVE-2026-100649

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100649/
Summaries are generated and may contain mistakes; the official description above is the record.