Iniciar sesión
Deutsch English Español Polski
Crítica

vLLM: OpenAI auth bypass

  • Publicada: 16.06.2026
  • Actualizado: 11.10.2026 15:17

Summary

A vulnerability in ASGI web servers and starlette's trust on those web servers enables an authentication bypass of the OpenAI API AuthenticationMiddleware, which was discovered during @x41sec's source code audit. It allows to use the API without providing the configured VLLM_API_KEY or --api-key.

Details

In https://github.com/vllm-project/vllm/blob/v0.14.0/vllm/entrypoints/openai/api_server.py#L689-L692 the url_path is taken from the URL, which is reconstructed by starlette based on the request scope.

python
from starlette.datastructures import URL, Headers, MutableHeaders, State

# ...

url_path = URL(scope=scope).path.removeprefix(root_path)
headers = Headers(scope=scope)
if url_path.startswith("/v1") and not self.verify_token(headers):
    response = JSONResponse(content={"error": "Unauthorized"}, status_code=401)
    return response(scope, receive, send)
return self.app(scope, receive, send)

The request scope includes the request's Host: header and reconstructs the URL as shown below:

python
f"{scheme}://{host_header}{path}"

Neither starlette nor any of the ASGI servers (including uvicorn, which vllm uses) properly filter the Host: header for invalid characters. This allows an attacker to include special URL characters such as / or ? in the Host: header and thereby control the reconstructed URL and it's .path attribute.

FastAPI/starlette's routing uses the HTTP path and does not depend on the parsed url.path attribute, allowing attackers to reach an endpoint via a certain path while providing a different value in the .path.

Impact

  • Instances of vllm that use an API Key for the OpenAI API and expose the API to attackers.
  • Instances behind an RFC-conforming web server (such as nginx) are not affected.

Software afectado

Haz clic en una tecnología para ver todas sus vulnerabilidades.

PlataformaPaqueteVersiones vulnerablesCorregida en
Python (PyPI) vllm >= 0.3.0, < 0.22.0 0.22.0

Referencias

Puntuación CVSS 9.1/10
Vector CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Debilidad (CWE)
CWE-444, CWE-501
Plataforma
Python (PyPI)
Paquete
vllm
Publicada
16.06.2026
Actualizado
11.10.2026 15:17

Fuentes y licencias

OSV / GitHub Advisory Database - PYSEC-2026-226 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-94f4-hr76-p5j6 - CC BY 4.0

Historial de vulnerabilidades: vllm

Todas las vulnerabilidades publicadas de este paquete (Python (PyPI)), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.

Todas (94) en el archivo
Entradas en total
94
Primera → última
09.2024 10.2026
Sin corrección
5
Explotada en ataques
0

Distribución por gravedad

  • Crítica 9
  • Alta 23
  • Media 47
  • Baja 4
  • Sin evaluar 11

Divulgaciones por año

Gravedad:
  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
    Alta · 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
    Alta · 7.5 CVE-2026-100652 >= 0.22.0, < 0.24.0 0.24.0
  3. vLLM has Remote DoS via Invalid Recovered Token Reinjection
    Alta · 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
    Alta · 7.5 CVE-2026-55574 < 0.24.0 0.24.0
  5. vLLM denial of service via prompt embeds on M-RoPE models
    Alta 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.
    Alta · 8.8 CVE-2026-54232 < 0.22.1 0.22.1
  7. vLLM: OpenAI auth bypass esta entrada
    Crítica · 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
    Alta · 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
    Alta · 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
    Alta · 8.8 CVE-2026-27893 >= 0.10.1, < 0.18.0 0.18.0
  11. vLLM has RCE In Video Processing
    Crítica · 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
    Alta · 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
    Alta · 8.8 CVE-2026-22807 >= 0.10.1, < 0.14.0 0.14.0
  14. vLLM introduced enhanced protection for CVE-2025-62164
    Alta · 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
    Alta · 7.1 CVE-2025-66448 < 0.11.1 0.11.1
  16. vLLM vulnerable to DoS with incorrect shape of multimodal embedding inputs
    Alta · 6.5 CVE-2025-62372 >= 0.5.5, < 0.11.1 0.11.1
  17. vLLM deserialization vulnerability leading to DoS and potential RCE
    Alta · 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
    Alta · 7.1 CVE-2025-6242 >= 0.5.0, < 0.11.0 0.11.0
  19. vLLM is vulnerable to timing attack at bearer auth
    Alta · 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
    Alta · 8.8 CVE-2025-9141 >= 0.10.0, < 0.10.1.1 0.10.1.1
Mostrar más (12) Mostrando 20 de 32

Identifica las vulnerabilidades de tu aplicación

Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.

Conectar tu aplicación
Newsletter DockRay

La seguridad de tus aplicaciones en tu correo

Vulnerabilidades importantes, recomendaciones concretas y consejos prácticos para tus aplicaciones. Elige tus tecnologías y sigue lo que importa para tu proyecto.

  • Un resumen diario de nuevas vulnerabilidades, también las críticas.
  • Avisos sobre actualizaciones importantes.
  • Consejos prácticos sobre seguridad y monitorización de aplicaciones.

Déjalo vacío para recibir avisos de todas las tecnologías.

Política de privacidad

Suscripción gratuita. Date de baja con un clic en cualquier correo.