Database/AI/ML frameworks & serving
vLLM (API key comparison): Timing attack recovers the API key
CVSS 7.5CVE-2025-59425AI/ML frameworks & servingcurated
Impact
Timing attack recovers the API key
Who can reach it
Unauthenticated network to the serving port
What to do
Upgrade to 0.11.0+; do not rely on vLLM's own API key as the tenant auth boundary — front it with a gateway
References
Related entries
- Transformers: attacker-supplied weight-decay regex patterns hang the training process (ReDoS)CVE-2025-6921 · Hugging Face Transformers (AdamWeightDecay optimizer regex matching)High
- NVIDIA OpenShell: cleartext HTTP/2 (h2c) inside a CONNECT tunnel bypasses L7 REST policyCVE-2026-100977 · NVIDIA OpenShell for Linux (L7 REST policy enforcement)High
- NVIDIA OpenShell: CLI diagnostic command escaped for one shell layer but run through two, allowing command injectionCVE-2026-100980 · NVIDIA OpenShell for Linux (CLI diagnostic interface)High
- MLflow: schemeless prompt source lets a caller read arbitrary files readable by the tracking serverCVE-2026-116690 · MLflow model registry (_create_model_version prompt branch / get-artifact)High
- vLLM orchestrator gateway: bearer tokens and full chat payloads written to persistent logsCVE-2026-15574 · vllm-orchestrator-gateway (Red Hat OpenShift AI)High
- SGLang (`/server_info`): Endpoint returns API keys and SSL keyfile pathsCVE-2026-15977 · SGLang (`/server_info`)High
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.