CVE-2026-44513

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 45% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m, epss
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Diffusers is the a library for pretrained diffusion models. Prior to 0.38.0, a trust_remote_code bypass in DiffusionPipeline.from_pretrained allows arbitrary remote code execution despite the user passing trust_remote_code=False (or omitting it, which is the default). The vulnerability has three variants, all sharing the same root cause — the trust_remote_code gate was implemented inside DiffusionPipeline.download() rather than at the actual dynamic-module load site, so any code path that bypassed or short-circuited download() also bypassed the security check. DiffusionPipeline.from_pretrained('repoA', custom_pipeline='attacker/repoB', trust_remote_code=False) — the gate evaluated against repoA's file list rather than repoB's, so repoB's pipeline.py was loaded and executed. DiffusionPipeline.from_pretrained('/local/snapshot', custom_pipeline='attacker/repoB', trust_remote_code=False) — the local-path branch never invoked download(), so the gate was never reached and remote code from repoB executed. DiffusionPipeline.from_pretrained('/local/snapshot', trust_remote_code=False) where the snapshot contains custom component files (e.g. unet/my_unet_model.py) referenced from model_index.json — same root cause; the local path skipped download() and custom component code executed. This vulnerability is fixed in 0.38.0.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
62%
KEV
Not listed

Published

May 14, 2026

Last Modified

July 22, 2026

Advisory Details (1)

Auto-updated May 14, 2026
Patch available. Sources: github.
github Patch Available

`trust_remote_code` bypass via `custom_pipeline` and local custom components · Advisory · huggingface/diffusers · GitHub

https://github.com/huggingface/diffusers/security/advisories/GHSA-98h9-4798-4q5v

Vendor Advisories for CVE-2026-44513(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
diffusers0.0.1 ... 0.9.0 (96 versions)0.38.0

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 128 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-23 17:39 UTCEG score recompute
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-22 01:51 UTCEG score recompute
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-20 19:36 UTCEG score recompute
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 10:23 UTCEG score recompute
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 03:56 UTCEG score recompute
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-14 02:25 UTCEG score recompute
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-12 14:59 UTCEG score recompute
  19. 2026-08-12 13:51 UTCEPSS rescore
  20. 2026-08-11 15:25 UTCEG score recompute
  21. 2026-08-11 00:52 UTCEG score recompute
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-09 14:28 UTCEG score recompute
  24. 2026-08-09 13:46 UTCEPSS rescore
  25. 2026-08-09 01:50 UTCEG score recompute
Show 75 more
  1. 2026-08-08 16:37 UTCEPSS rescore
  2. 2026-08-08 02:35 UTCEG score recompute
  3. 2026-08-07 01:20 UTCEG score recompute
  4. 2026-08-06 13:46 UTCEPSS rescore
  5. 2026-08-05 21:36 UTCEG score recompute
  6. 2026-08-05 19:17 UTCEPSS rescore
  7. 2026-08-04 15:10 UTCEPSS rescore
  8. 2026-08-04 10:38 UTCEPSS rescore
  9. 2026-08-03 19:00 UTCEG score recompute
  10. 2026-08-03 10:36 UTCEPSS rescore
  11. 2026-08-02 08:00 UTCEG score recompute
  12. 2026-08-02 02:27 UTCEPSS rescore
  13. 2026-08-01 19:21 UTCEG score recompute
  14. 2026-08-01 04:16 UTCEPSS rescore
  15. 2026-07-30 16:28 UTCEPSS rescore
  16. 2026-07-30 01:30 UTCEPSS rescore
  17. 2026-07-28 15:36 UTCEPSS rescore
  18. 2026-07-27 14:13 UTCEPSS rescore
  19. 2026-07-26 14:54 UTCEPSS rescore
  20. 2026-07-26 14:54 UTCEPSS rescore
  21. 2026-07-25 14:18 UTCEPSS rescore
  22. 2026-07-24 14:17 UTCEPSS rescore
  23. 2026-07-23 14:18 UTCEPSS rescore
  24. 2026-07-23 03:15 UTCEG score recompute
  25. 2026-07-22 14:08 UTCEPSS rescore
  26. 2026-07-21 15:24 UTCEPSS rescore
  27. 2026-07-20 17:08 UTCEPSS rescore
  28. 2026-07-19 14:31 UTCEPSS rescore
  29. 2026-07-19 02:29 UTCEPSS rescore
  30. 2026-07-18 10:04 UTCEPSS rescore
  31. 2026-07-18 01:29 UTCOSV refresh
  32. 2026-07-16 17:03 UTCEPSS rescore
  33. 2026-07-15 16:57 UTCEPSS rescore
  34. 2026-07-15 02:00 UTCEPSS rescore
  35. 2026-07-13 22:30 UTCEPSS rescore
  36. 2026-07-13 06:13 UTCEPSS rescore
  37. 2026-07-12 05:46 UTCEPSS rescore
  38. 2026-07-11 08:27 UTCEPSS rescore
  39. 2026-07-09 19:10 UTCEPSS rescore
  40. 2026-07-08 15:16 UTCEPSS rescore
  41. 2026-07-07 13:46 UTCEPSS rescore
  42. 2026-07-06 16:27 UTCEPSS rescore
  43. 2026-07-06 02:23 UTCEPSS rescore
  44. 2026-07-05 02:30 UTCEPSS rescore
  45. 2026-07-04 06:31 UTCEPSS rescore
  46. 2026-07-01 15:07 UTCEPSS rescore
  47. 2026-06-30 23:22 UTCEPSS rescore
  48. 2026-06-29 14:06 UTCEPSS rescore
  49. 2026-06-28 14:07 UTCEPSS rescore
  50. 2026-06-28 04:56 UTCEPSS rescore
  51. 2026-06-27 03:08 UTCEPSS rescore
  52. 2026-06-25 13:49 UTCEPSS rescore
  53. 2026-06-25 13:49 UTCEPSS rescore
  54. 2026-06-24 14:05 UTCEPSS rescore
  55. 2026-06-23 21:33 UTCEPSS rescore
  56. 2026-06-22 14:25 UTCEPSS rescore
  57. 2026-06-22 14:25 UTCEPSS rescore
  58. 2026-06-21 14:56 UTCEPSS rescore
  59. 2026-06-21 14:56 UTCEPSS rescore
  60. 2026-06-21 01:59 UTCEPSS rescore
  61. 2026-06-19 19:25 UTCEPSS rescore
  62. 2026-06-18 17:52 UTCEPSS rescore
  63. 2026-06-18 17:52 UTCEPSS rescore
  64. 2026-06-17 17:53 UTCEPSS rescore
  65. 2026-06-16 17:52 UTCEPSS rescore
  66. 2026-06-15 17:49 UTCEPSS rescore
  67. 2026-06-13 23:00 UTCEPSS rescore
  68. 2026-06-12 23:12 UTCEPSS rescore
  69. 2026-06-12 23:12 UTCEPSS rescore
  70. 2026-06-11 14:00 UTCEPSS rescore
  71. 2026-06-10 22:18 UTCEPSS rescore
  72. 2026-06-10 13:22 UTCEPSS rescore
  73. 2026-06-10 13:22 UTCEPSS rescore
  74. 2026-06-08 14:17 UTCEPSS rescore
  75. 2026-06-08 14:17 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-44513?
CVE-2026-44513 is a high vulnerability published on May 14, 2026. Diffusers is the a library for pretrained diffusion models. Prior to 0.38.0, a trustremotecode bypass in DiffusionPipeline.frompretrained allows arbitrary remote code execution despite the user passing trustremotecode=False (or omitting it, which is the default). The vulnerability has three…
When was CVE-2026-44513 disclosed?
CVE-2026-44513 was first published in the National Vulnerability Database on May 14, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44513 actively exploited?
CVE-2026-44513 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 37.7% of all scored CVEs.
What is the CVSS score of CVE-2026-44513?
CVE-2026-44513 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-44513?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44513, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44513

Explore →

Is Your Infrastructure Affected by CVE-2026-44513?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.