← Back
CVE-2026-12491
medium
CVSS 4.8
Vulnerability in vllm (CVE-2026-12491)
Summary
vulnerability in vllm (CVE-2026-12491). Risk of unauthorized operations or information disclosure. Exploitable via ``ImageOps.exif_transpose``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-12491** has been found in vllm.
Attackers can target a specific entry point like ``ImageOps.exif_transpose`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "vllm CVE-2026-12491" on the vendor's site.
CVE-2026-12491 (vllm) — CWE-115 / CVSS v3 4.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `ImageOps.exif_transpose` / `tRNS` / `rescale_image_size` / `transpose`
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-115) exists in vllm. Attackers reach the vulnerable code path via ``ImageOps.exif_transpose`` without authentication.
📍 Affected scope
vllm — . Attack surface: `ImageOps.exif_transpose` / `tRNS` / `rescale_image_size` / `transpose`.
🔥 Severity
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
vllm
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- web https://nvd.nist.gov/vuln/detail/CVE-2026-12491
- web [email protected]
- web [email protected]
- web https://github.com/advisories/GHSA-x8xr-mj9x-6h7w
- web https://github.com/vllm-project/vllm/security/advisories/GHSA-8jr5-v98p-w75m
- web https://github.com/vllm-project/vllm/pull/44974
- web https://github.com/vllm-project/vllm/commit/cf1c90672404548aa3bc51f92c4745576a65ee26
- web https://github.com/advisories/GHSA-8jr5-v98p-w75m