CVE-2026-80047

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-01. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week

Also known asEUVD-2026-69144 (ENISA EUVD) · GHSA-x9r9-c232-4q39 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (CERT/CC) lists Hugging Face Transformers versions 4.57.0 up to and including 5.16.1 as affected. No release containing a fix is confirmed on record.

A vulnerability in Hugging Face Transformers (versions 4.57.0 to 5.16.1) allows remote Python files to be written to local disk without user consent when using GenerativePreTrainedModel.load_custom_generate(). The function fetches and caches a remote module file before performing the required trust_remote_code consent check, inverting the security model enforced by other code-loading paths (such as AutoConfig, AutoModel, and AutoTokenizer). As a result, attacker‑controlled Python code from custom_generate/generate.py is copied into the user’s ~/.cache/huggingface/modules directory even if the user declines the trust prompt. Although execution is correctly gated, the file write is not reversible and can persist across sessions. This can lead to persistent, unauthorized files on disk and stale cache collisions where cached attacker code may later be executed during trusted model loads. The issue stems from an unconditional file write in dynamic_module_utils.py prior to any trust verification.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
<0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.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 or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

Exploitation none (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.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

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

September 1, 2026

Last Modified

September 23, 2026

Advisory Details (2)

Auto-updated Sep 3, 2026
No fix on record yet. Sources: cert.
CERT

VU#456290 - Hugging Face Transformers library writes remote code to disk prior to consent check

https://kb.cert.org/vuls/id/456290
Web page

GitHub - huggingface/transformers: 🤗 Transformers: the model-definition framework for state-of-the-art machine learning models in text, vision, audio, and multimodal models, for both inference and training. · GitHub

https://github.com/huggingface/transformers

Vendor Advisories for CVE-2026-80047(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
piptransformers—ghsa

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
transformers4.49.0 ... 5.8.1 (55 versions)
  • 4.49.0 through 5.8.1: no fix on record
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 52× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 161 refreshes 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 61 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-80047?
CVE-2026-80047 is a high-severity vulnerability; its CVE record was published on September 1, 2026. A vulnerability in Hugging Face Transformers (versions 4.57.0 to 5.16.1) allows remote Python files to be written to local disk without user consent when using GenerativePreTrainedModel.load_custom_generate(). The function fetches and caches a remote module file before performing the required…
When was the CVE record for CVE-2026-80047 published?
The CVE record for CVE-2026-80047 was published on September 1, 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 September 23, 2026; the record at its source may have been updated since.
Is CVE-2026-80047 actively exploited?
CVE-2026-80047 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80047?
CVE-2026-80047 has a CVSS v3.1 base score of 7.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-80047?
No fix for CVE-2026-80047 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (CERT/CC) lists Hugging Face Transformers versions 4.57.0 up to and including 5.16.1 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-80047 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-80047

Explore →

Is Your Infrastructure Affected by CVE-2026-80047?

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

Book a Demo →Browse All CVEs