Sign in Sign up
JA · EN · FR
SecPulse
This advisory has been withdrawn (2026-05-07).
Categories
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.

Original description

The description as published by the source.

Background

This vulnerability is found in the DiffusionPipeline.from_pretrained flow, which is used to load a pipeline from the HuggingFace Hub.

This function accepts an optional custom_pipeline keyword argument: the name of a Python file in the repo that contains a custom class inheriting from DiffusionPipeline. An equivalent flow is triggered when the _class_name field in model_index.json (the repo config file) is set to a custom class.

Any attempt to use a custom pipeline throws the following exception, requesting that trust_remote_code is also passed:

DiffusionPipeline.from_pretrained(
    pretrained_model_name_or_path='ido-shani/custom-pipeline',
    custom_pipeline="custom"
)

ValueError: The repository for ido-shani/custom-pipeline contains custom code in
custom.py which must be executed to correctly load the model. You can inspect the
repository content at https://hf.co/ido-shani/custom-pipeline/blob/main/custom.py.
Please pass the argument `trust_remote_code=True` to allow custom code to be run.

The vulnerability is a silent RCE - it allows arbitrary code to be loaded through the custom_pipeline flow from a Hub repo, with no custom_pipeline or trust_remote_code kwargs and nothing suspicious in the config. The from_pretrained call succeeds and returns a functional pipeline.

Naive Flow

First, all relevant arguments are popped from kwargs and stored in local variables.

Given a pretrained_model_name_or_path that is a Hub r…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

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

Check the vendor advisory for the affected versions of 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'diffusers' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で diffusers を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade diffusers to 0.38.0

    ステージング環境で 0.38.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

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

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details