CVE-2026-44827

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.7% (54th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-30332 (ENISA EUVD) · PYSEC-2026-41 (OSV.dev)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Diffusers is the a library for pretrained diffusion models. Prior to 0.38.0, diffusers 0.37.0 allows remote code execution without the trust_remote_code=True safeguard when loading pipelines from Hugging Face Hub repositories. The _resolve_custom_pipeline_and_cls function in pipeline_loading_utils.py performs string interpolation on the custom_pipeline parameter using f"{custom_pipeline}.py". When custom_pipeline is not supplied by the user, it defaults to None, which Python interpolates as the literal string "None.py". If an attacker publishes a Hub repository containing a file named None.py with a class that subclasses DiffusionPipeline, the file is automatically downloaded and executed during a standard DiffusionPipeline.from_pretrained() call with no additional keyword arguments. The trust_remote_code check in DiffusionPipeline.download() is bypassed because it evaluates custom_pipeline is not None as False (since the kwarg was never supplied), while the downstream code path that actually loads the module resolves the None value into a valid filename. An attacker can achieve silent arbitrary code execution by publishing a malicious model repository with a None.py file and a standard-looking model_index.json that references a legitimate pipeline class name, requiring only that a victim calls from_pretrained on the repository. This vulnerability is fixed in 0.38.0.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
54th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 14, 2026

Last Modified

October 26, 2026

Advisory Details (1)

Auto-updated May 14, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

None.py Trust Remote Code Bypass · Advisory · huggingface/diffusers · GitHub

https://github.com/huggingface/diffusers/security/advisories/GHSA-j7w6-vpvq-j3gm

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhelai3/disk-image-cuda-rhel9:17909574172026-10-05redhat
redhatrhelai3/bootc-gcp-cuda-rhel9:17908811232026-10-05redhat
redhatrhaii/vllm-cpu-rhel9:17900757932026-09-23redhat
redhatrhaii/vllm-cuda-rhel9:17900901312026-09-23redhat
redhatrhaii/vllm-cpu-rhel9:17896811282026-09-21redhat
redhatrhaii/vllm-cuda-rhel9:17896811262026-09-21redhat
redhatrhoai/odh-training-rocm64-torch29-py312-rhel9:17866114352026-08-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
diffusers0.0.1 ... 0.9.0 (96 versions)
  • every version up to 0.38.0: fixed in 0.38.0
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 216 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 116 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-44827?
CVE-2026-44827 is a high-severity vulnerability; its CVE record was published on May 14, 2026. Diffusers is the a library for pretrained diffusion models. Prior to 0.38.0, diffusers 0.37.0 allows remote code execution without the trust_remote_code=True safeguard when loading pipelines from Hugging Face Hub repositories. The _resolve_custom_pipeline_and_cls function in…
When was the CVE record for CVE-2026-44827 published?
The CVE record for CVE-2026-44827 was published on May 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-44827 actively exploited?
CVE-2026-44827 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44827?
CVE-2026-44827 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-44827?
A fix for CVE-2026-44827 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44827 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-44827?

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