CVE-2026-65920 diffusers vulnerability
Diffusers through 0.39.0, fixed in commit cee298c, contains a path traversal vulnerability in the _get_checkpoint_shard_files function that allows attackers to read arbitrary files by supplying malicious weight_map values in model index JSON. Attackers can use ../ sequences or absolute paths in weight_map entries to escape the model directory and read safetensors files outside the intended location during model loading.
Browse Path Traversal security risksQuick answer
huggingface diffusers should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- <= 0.39.0
Fixed versions
- cee298c1f37c439a9a408396b8283a921238a1c6
How to fix it
CVE-2026-65920 affects diffusers and involves file access or path traversal. Successful exploitation may read, overwrite, or delete files outside the intended directory. Prioritize deployments that process untrusted input, expose the affected feature, or hold sensitive data. Upgrade diffusers to cee298c1f37c439a9a408396b8283a921238a1c6 or a later vendor-supported fixed release.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses diffusers.
- Compare the installed version with the recorded affected range: <= 0.39.0.
- Upgrade diffusers to cee298c1f37c439a9a408396b8283a921238a1c6 or a later vendor-supported fixed release.
- Until patched, reject absolute and parent-relative paths, confine filesystem access to an explicit root, and accept files or manifests only from trusted sources.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to diffusers; remove access that is not required.
- Review filesystem, application, and audit logs for parent-directory segments, absolute paths, unexpected reads, writes, or deletions outside the intended root.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-65920 in place.
- Use a safe regression test to confirm the affected file access or path traversal path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
Trusted references
FAQ
What is affected by CVE-2026-65920?
huggingface diffusers versions listed as affected should be reviewed: <= 0.39.0.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.