CVE-2026-80047
HIGHDescription
A vulnerability in Hugging Face Transformers (versions >= 4.49.0 and <= 5.8.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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 0% of all known CVEs.
References
Related Vulnerabilities
Other CWE-273 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2011-2921 | Critical | 9.8 | 83% | - | - |
| CVE-2024-38813 | High | 7.5 | 17% | KEV | Fix |
| CVE-2017-6972 | Critical | 9.8 | 15% | - | - |
| CVE-2015-0278 | High | 10.0 | 3.2% | - | Fix |
| CVE-2019-18276 | High | 7.8 | 2.6% | - | Fix |
| CVE-2021-36372 | Critical | 9.8 | 2.5% | - | Fix |
Common questions
How do I fix CVE-2026-80047?
No published fix for CVE-2026-80047 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-80047 being actively exploited?
Not that we know of. CVE-2026-80047 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.08% is the estimated probability that it will be exploited in the next 30 days. That is higher than 0% of all scored CVEs.
How severe is CVE-2026-80047?
CVE-2026-80047 has a CVSS v3 base score of 7.8, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-80047
Markdown
[](https://tridentstack.com/cve/CVE-2026-80047)HTML
<a href="https://tridentstack.com/cve/CVE-2026-80047"><img src="https://tridentstack.com/cve/badge/CVE-2026-80047.svg" alt="CVE-2026-80047"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-03.