← Back
CVE-2026-44827
high
CVSS 8.8
Code Injection in diffusers (CVE-2026-44827)
Summary
code injection in diffusers (CVE-2026-44827). Successful exploitation can lead to full system takeover. Exploitable via ``DiffusionPipeline.from_pretrained``. Mitigation: upgrade to `0.38.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44827** has been found in diffusers.
Attackers can target a specific entry point like ``DiffusionPipeline.from_pretrained`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade diffusers to **0.38.0** or later.
If unsure, ask your IT team or search "diffusers CVE-2026-44827" on the vendor's site.
CVE-2026-44827 (diffusers) — CWE-94 / CVSS v3 8.8
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `DiffusionPipeline.from_pretrained` / `custom_pipeline` / `DiffusionPipeline` / `_class_name`
Patched: `0.38.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
**arbitrary code execution** (CWE-94) exists in diffusers. Attackers reach the vulnerable code path via ``DiffusionPipeline.from_pretrained`` without authentication.
📍 Affected scope
diffusers — . Attack surface: `DiffusionPipeline.from_pretrained` / `custom_pipeline` / `DiffusionPipeline` / `_class_name`.
🔥 Severity
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **0.38.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 'diffusers' .` 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 'diffusers' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `diffusers` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade diffusers to 0.38.0ステージング環境で 0.38.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
diffusers
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.38.0"}]}]
PyPI
diffusers
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.38.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-44827
- package https://github.com/huggingface/diffusers
- web https://github.com/huggingface/diffusers/security/advisories/GHSA-j7w6-vpvq-j3gm
- web https://github.com/huggingface/diffusers/pull/13448
- web https://github.com/huggingface/diffusers/commit/a37f6f8394ac2a7ee8360c3abea811efe54512b1
- web https://github.com/huggingface/diffusers/releases/tag/v0.38.0
- web https://github.com/advisories/GHSA-j7w6-vpvq-j3gm
- web https://github.com/pypa/advisory-database/tree/main/vulns/diffusers/PYSEC-2026-41.yaml