CVE-2026-105760: vLLM GLMGA Video Sampling Permits Request-driven Vulnerability

MODERATE
Advisory Identifier: GHSA-58v5-2m8f-94pr
CVSS 5.3
CWE-400
Published
Advisory Summary

CVE-2026-105760 is a MODERATE (CVSS 5.3) glmga video sampling permits request-driven vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting vLLM libraries in the PyPI ecosystem. The issue involves glmga video sampling permits request-driven cpu and memory exhaustion. Remediation is available by upgrading affected packages to version 0.30.0.

CVE-2026-105760 at a Glance

CVE Identifier CVE-2026-105760
GHSA Identifier GHSA-58v5-2m8f-94pr
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-400: Uncontrolled Resource Consumption
Affected Product vLLM
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability Low (A:L)

How to Fix CVE-2026-105760

To remediate this vulnerability, upgrade all affected vLLM dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

vllm fixed: 0.30.0
pip install vllm>=0.30.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show vllm

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-105760, inspect your installed packages using pip:

pip show vllm

Analyze the terminal output to locate any version of vLLM in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.30.0), your application is affected.

Note: The pip show vllm command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In vLLM, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary The OpenAI-compatible chat endpoint accepts request-level video loader options through `media_io_kwargs`. A caller can select the GLMGA sampler and provide large `fps` and `max_frames` values. GLMGA first constructs an attacker-sized Python index list and then deduplicates it, even when the supplied video contains only a few frames. This work occurs in the shared media-loading executor before frame reads, allowing a tiny valid video and compact JSON options to consume disproportionate CPU time and memory and delay unrelated media requests. The demonstrated impact is partial denial of service. No memory corruption, data disclosure, or code execution is claimed. ## Affected configuration The server must expose chat completions for a video-capable model and accept request-level `media_io_kwargs`. The model does not need to use GLMGA by default because the request value overrides the model's loader mapping. The proof of concept uses an inline two-frame video and explicitly selects the OpenCV decoder, so no external media host or GPU decoder is required. The request is reachable without vLLM credentials when no API key is configured. With API-key authentication enabled, any caller holding a valid key can reach the same path. ## Attack surface A remote caller submits a valid chat-completion request with a small video and the following request-level options: ```json { "media_io_kwargs": { "video": { "video_backend": "glmga", "backend": "opencv", "fps": 500000, "max_frames": 500000 } } } ``` Increasing both numeric values increases temporary list construction and deduplication work even when the final decoded frame set remains unchanged. ## Root cause 1. `ChatCompletionRequest` exposes `media_io_kwargs` as request-controlled nested values: [`protocol.py#L365-L371`](https://github.com/vllm-project/vllm/blob/570735520942b6428ae98f1eb442c6d88adae55e/vllm/entrypoints/openai/chat_completion/protocol.py#L365-L371). 2. The request options are carried into chat parameters without a numeric work bound on GLMGA's `fps` or `max_frames`: [`protocol.py#L571-L599`](https://github.com/vllm-project/vllm/blob/570735520942b6428ae98f1eb442c6d88adae55e/vllm/entrypoints/openai/chat_completion/protocol.py#L571-L599). 3. Media options are merged so request values override configured defaults, including `video_backend`: [`connector.py#L577-L605`](https://github.com/vllm-project/vllm/blob/570735520942b6428ae98f1eb442c6d88adae55e/vllm/multimodal/media/connector.py#L577-L605). 4. The connector selects a registered video loader and runs media loading through the shared executor: [`video.py#L28-L66`](https://github.com/vllm-project/vllm/blob/570735520942b6428ae98f1eb442c6d88adae55e/vllm/multimodal/media/video.py#L28-L66) and [`connector.py#L44-L47`](https://github.com/vllm-project/vllm/blob/570735520942b6428ae98f1eb442c6d88adae55e/vllm/multimodal/media/connector.py#L44-L47). 5. GLMGA calculates `extract_t = min(int(duration * fps), max_frames)`, builds a list with that many entries, and deduplicates it before decoding frames: [`video.py#L667-L740`](https://github.com/vllm-project/vllm/blob/570735520942b6428ae98f1eb442c6d88adae55e/vllm/multimodal/video.py#L667-L740). 6. The OpenCV decoder receives the already-deduplicated indices, so a two-frame file can trigger a large intermediate allocation while producing only two decoded frames: [`opencv.py#L28-L50`](https://github.com/vllm-project/vllm/blob/570735520942b6428ae98f1eb442c6d88adae55e/vllm/multimodal/video_decoders/opencv.py#L28-L50). The missing invariant is a strict upper bound on sampling work before the index list is constructed. Bounding decoded output after deduplication does not bound the vulnerable intermediate computation. ## Suggested remediation Validate request-level video sampling options before dispatching work to the media executor. Enforce conservative absolute limits for `fps`, `max_frames`, and especially the computed candidate count. Reject non-finite, negative, or otherwise invalid numeric values. Avoid constructing `O(extract_t)` intermediate Python lists. Generate bounded unique frame indices directly from the source frame count and output-frame limit. Apply the limit before list construction and before shared executor submission. Add tests showing that extreme request values are rejected or consume constant memory for a fixed output-frame count. ## Workarounds - Remove or filter request-level `video_backend`, `fps`, and `max_frames` options at the gateway. - Do not allow untrusted callers to select GLMGA. - Apply authentication, rate limiting, request concurrency limits, and process memory isolation. - Use a separate constrained media-loading worker pool where operationally feasible. - Existing media byte, pixel, or decoded-frame limits do not necessarily bound this pre-decode candidate-index allocation. ## Related advisory [GHSA-cqm8-jxg6-fqfq](https://github.com/vllm-project/vllm/security/advisories/GHSA-cqm8-jxg6-fqfq) concerns partial denial of service in the DeepStream video backend through backend confusion and insufficient pixel guarding. This report concerns a different CPU-side GLMGA algorithm: request-controlled sampling values create a large redundant index list before the OpenCV decoder reads a fixed, tiny frame set. The vulnerable backend, resource sink, and required remediation differ.

CVE-2026-105760 Affected vLLM Versions

1 component(s)
Fixed Versions:
0.30.0
Product / Package Ecosystem Affected Versions Fixed Version
vllm
PyPI
≥ 0.23.0rc2
< 0.30.0
0.30.0

References

Frequently Asked Questions

What is CVE-2026-105760?
CVE-2026-105760 is a security vulnerability in vLLM involving GLMGA video sampling permits request-driven CPU and memory exhaustion under CWE-400: Uncontrolled Resource Consumption.
Which vLLM versions are affected?
Affected versions include releases prior to 0.30.0 across affected packages: vllm.
What version fixes CVE-2026-105760?
Upgrading to 0.30.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is vllm affected?
Yes, vllm is affected in releases prior to 0.30.0. Upgrade your dependency to 0.30.0 or later.
What is the CVSS score of CVE-2026-105760?
CVE-2026-105760 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.
What CWE is associated with CVE-2026-105760?
CVE-2026-105760 is classified under CWE-400: Uncontrolled Resource Consumption (The product does not properly control the allocation and maintenance of a limited resource.).
How can I check PyPI dependencies for CVE-2026-105760?
Run the dependency tree command: 'pip show vllm'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-58v5-2m8f-94pr",
  "modified" : "2026-10-05T23:42:55Z",
  "published" : "2026-10-05T23:42:55Z",
  "aliases" : [ "CVE-2026-105760" ],
  "summary" : "vLLM: GLMGA video sampling permits request-driven CPU and memory exhaustion",
  "details" : "## Summary\n\nThe OpenAI-compatible chat endpoint accepts request-level video loader options through `media_io_kwargs`. A caller can select the GLMGA sampler and provide large `fps` and `max_frames` values. GLMGA first constructs an attacker-sized Python index list and then deduplicates it, even when the supplied video contains only a few frames. This work occurs in the shared media-loading executor before frame reads, allowing a tiny valid video and compact JSON options to consume disproportionate CPU time and memory and delay unrelated media requests.\n\nThe demonstrated impact is partial denial of service. No memory corruption, data disclosure, or code execution is claimed.\n\n## Affected configuration\n\nThe server must expose chat completions for a video-capable model and accept request-level `media_io_kwargs`. The model does not need to use GLMGA by default because the request value overrides the model's loader mapping. The proof of concept uses an inline two-frame video and explicitly selects the OpenCV decoder, so no external media host or GPU decoder is required.\n\nThe request is reachable without vLLM credentials when no API key is configured. With API-key authentication enabled, any caller holding a valid key can reach the same path.\n\n## Attack surface\n\nA remote caller submits a valid chat-completion request with a small video and the following request-level options:\n\n```json\n{\n  \"media_io_kwargs\": {\n    \"video\": {\n      \"video_backend\": \"glmga\",\n      \"backend\": \"opencv\",\n      \"fps\": 500000,\n      \"max_frames\": 500000\n    }\n  }\n}\n```\n\nIncreasing both numeric values increases temporary list construction and deduplication work even when the final decoded frame set remains unchanged.\n\n## Root cause\n\n1. `ChatCompletionRequest` exposes `media_io_kwargs` as request-controlled nested values: [`protocol.py#L365-L371`](https://github.com/vllm-project/vllm/blob/570735520942b6428ae98f1eb442c6d88adae55e/vllm/entrypoints/openai/chat_completion/protocol.py#L365-L371).\n2. The request options are carried into chat parameters without a numeric work bound on GLMGA's `fps` or `max_frames`: [`protocol.py#L571-L599`](https://github.com/vllm-project/vllm/blob/570735520942b6428ae98f1eb442c6d88adae55e/vllm/entrypoints/openai/chat_completion/protocol.py#L571-L599).\n3. Media options are merged so request values override configured defaults, including `video_backend`: [`connector.py#L577-L605`](https://github.com/vllm-project/vllm/blob/570735520942b6428ae98f1eb442c6d88adae55e/vllm/multimodal/media/connector.py#L577-L605).\n4. The connector selects a registered video loader and runs media loading through the shared executor: [`video.py#L28-L66`](https://github.com/vllm-project/vllm/blob/570735520942b6428ae98f1eb442c6d88adae55e/vllm/multimodal/media/video.py#L28-L66) and [`connector.py#L44-L47`](https://github.com/vllm-project/vllm/blob/570735520942b6428ae98f1eb442c6d88adae55e/vllm/multimodal/media/connector.py#L44-L47).\n5. GLMGA calculates `extract_t = min(int(duration * fps), max_frames)`, builds a list with that many entries, and deduplicates it before decoding frames: [`video.py#L667-L740`](https://github.com/vllm-project/vllm/blob/570735520942b6428ae98f1eb442c6d88adae55e/vllm/multimodal/video.py#L667-L740).\n6. The OpenCV decoder receives the already-deduplicated indices, so a two-frame file can trigger a large intermediate allocation while producing only two decoded frames: [`opencv.py#L28-L50`](https://github.com/vllm-project/vllm/blob/570735520942b6428ae98f1eb442c6d88adae55e/vllm/multimodal/video_decoders/opencv.py#L28-L50).\n\nThe missing invariant is a strict upper bound on sampling work before the index list is constructed. Bounding decoded output after deduplication does not bound the vulnerable intermediate computation.\n\n\n## Suggested remediation\n\nValidate request-level video sampling options before dispatching work to the media executor. Enforce conservative absolute limits for `fps`, `max_frames`, and especially the computed candidate count. Reject non-finite, negative, or otherwise invalid numeric values.\n\nAvoid constructing `O(extract_t)` intermediate Python lists. Generate bounded unique frame indices directly from the source frame count and output-frame limit. Apply the limit before list construction and before shared executor submission. Add tests showing that extreme request values are rejected or consume constant memory for a fixed output-frame count.\n\n## Workarounds\n\n- Remove or filter request-level `video_backend`, `fps`, and `max_frames` options at the gateway.\n- Do not allow untrusted callers to select GLMGA.\n- Apply authentication, rate limiting, request concurrency limits, and process memory isolation.\n- Use a separate constrained media-loading worker pool where operationally feasible.\n- Existing media byte, pixel, or decoded-frame limits do not necessarily bound this pre-decode candidate-index allocation.\n\n## Related advisory\n\n[GHSA-cqm8-jxg6-fqfq](https://github.com/vllm-project/vllm/security/advisories/GHSA-cqm8-jxg6-fqfq) concerns partial denial of service in the DeepStream video backend through backend confusion and insufficient pixel guarding. This report concerns a different CPU-side GLMGA algorithm: request-controlled sampling values create a large redundant index list before the OpenCV decoder reads a fixed, tiny frame set. The vulnerable backend, resource sink, and required remediation differ.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "vllm"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.23.0rc2"
      }, {
        "fixed" : "0.30.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/vllm-project/vllm/security/advisories/GHSA-58v5-2m8f-94pr"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/vllm-project/vllm/pull/54935"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/vllm-project/vllm/commit/8b6de0eb9a09ef53f20cf06bd4d17ee264b9c2a7"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/vllm-project/vllm"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/vllm-project/vllm/releases/tag/v0.30.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-400" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-05T23:42:55Z",
    "nvd_published_at" : null
  }
}