← Back
CVE-2026-22773
Vulnerability in vllm (CVE-2026-22773)
Summary
vulnerability in vllm (CVE-2026-22773). Risk of unauthorized operations or information disclosure. Exploitable via ``num_patches``. Mitigation: upgrade to `0.12.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-22773** has been found in vllm.
Attackers can target a specific entry point like ``num_patches`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade vllm to **0.12.0** or later.
If unsure, ask your IT team or search "vllm CVE-2026-22773" on the vendor's site.
CVE-2026-22773 (vllm) — CWE-770 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `num_patches`
Patched: `0.12.0` — 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 ``num_patches`` without authentication.
📍 Affected scope
vllm — . Attack surface: `num_patches`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.12.0**.
🛡️ 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.12.0ステージング環境で 0.12.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
vllm
[{"type":"ECOSYSTEM","events":[{"introduced":"0.6.4"},{"fixed":"0.12.0"}]}]
pip
vllm
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.12.0"}]}]
References
- advisory https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/22xxx/CVE-2026-22773.json
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-22773
- package https://github.com/vllm-project/vllm
- web https://github.com/vllm-project/vllm/security/advisories/GHSA-grg2-63fw-f2qr
- web https://github.com/vllm-project/vllm/pull/29881
- web https://github.com/vllm-project/vllm/commit/0ec84221718d920c3f46da879cc354f94b8fb59e
- web https://github.com/pypa/advisory-database/tree/main/vulns/vllm/PYSEC-2026-143.yaml
- web https://github.com/advisories/GHSA-grg2-63fw-f2qr