← Back
CVE-2025-62426
Vulnerability in vllm (CVE-2025-62426)
Summary
vulnerability in vllm (CVE-2025-62426). Risk of unauthorized operations or information disclosure. Exploitable via ``chat_template_kwargs``. Mitigation: upgrade to `0.11.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-62426** has been found in vllm.
Attackers can target a specific entry point like ``chat_template_kwargs`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade vllm to **0.11.1** or later.
If unsure, ask your IT team or search "vllm CVE-2025-62426" on the vendor's site.
CVE-2025-62426 (vllm) — CWE-770 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `chat_template_kwargs` / `apply_hf_chat_template` / `tokenize` / `_preprocess_chat`
Patched: `0.11.1` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-770) exists in vllm. Attackers reach the vulnerable code path via ``chat_template_kwargs`` without authentication.
📍 Affected scope
vllm — . Attack surface: `chat_template_kwargs` / `apply_hf_chat_template` / `tokenize` / `_preprocess_chat`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.11.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'vllm' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'vllm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `vllm` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade vllm to 0.11.1ステージング環境で 0.11.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
vllm
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.11.1"}]}]
PyPI
vllm
[{"type":"ECOSYSTEM","events":[{"introduced":"0.5.5"},{"fixed":"0.11.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-62426
- advisory https://github.com/advisories/GHSA-69j4-grxj-j64p
- package https://github.com/vllm-project/vllm
- package https://pypi.org/project/vllm
- web https://github.com/vllm-project/vllm/security/advisories/GHSA-69j4-grxj-j64p
- web https://github.com/vllm-project/vllm/pull/27205
- web https://github.com/vllm-project/vllm/commit/3ada34f9cb4d1af763fdfa3b481862a93eb6bd2b
- web https://github.com/vllm-project/vllm/blob/2a6dc67eb520ddb9c4138d8b35ed6fe6226997fb/vllm/entrypoints/chat_utils.py#L1602-L1610
- web https://github.com/vllm-project/vllm/blob/2a6dc67eb520ddb9c4138d8b35ed6fe6226997fb/vllm/entrypoints/openai/serving_engine.py#L809-L814
- web https://github.com/pypa/advisory-database/tree/main/vulns/vllm/PYSEC-2026-2012.yaml