CVE-2026-4372

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-05-26. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-31598 (ENISA EUVD) · GHSA-29pf-2h5f-8g72 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A critical remote code execution vulnerability exists in all versions of the HuggingFace transformers library prior to version 5.3.0. The vulnerability allows an attacker to craft a malicious config.json file containing the _attn_implementation_internal field set to an attacker-controlled HuggingFace Hub repository ID. When a victim loads this model using the standard AutoModelForCausalLM.from_pretrained() API, the library downloads and executes arbitrary Python code from the attacker's repository with the victim's full OS privileges. This issue arises due to unfiltered deserialization of configuration attributes, insufficient sanitization of internal fields, and unsandboxed execution of downloaded kernels. The vulnerability bypasses the trust_remote_code security mechanism, is invisible to the victim, and exploits the standard documented usage pattern, making it particularly severe. Users are advised to upgrade to version 5.3.0 or later to mitigate this issue.

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.7% × 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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
53rd
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.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). 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.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).

A fix is available. Apply it within your standard update timelines.

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.

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 24, 2026

Last Modified

July 23, 2026

Advisory Details (2)

Auto-updated Jun 4, 2026
Patch available. Sources: github_commit.
Web page

huntr - The world’s first bug bounty platform for AI/ML

https://huntr.com/bounties/1f693a6e-6836-4b8b-a0bd-ca036fba8884
GitHub commit

commit a7f8e7ff37d8 (huggingface/transformers)

Fix landed in huggingface/transformers commit a7f8e7ff37d8 — awaiting tagged release

https://github.com/huggingface/transformers/commit/a7f8e7ff37d87d1a1a0c8cf607971c607741452f

Vendor Advisories for CVE-2026-4372(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 rangeFix by version rangeDependents
transformers0.1 ... 5.2.0 (212 versions)
  • every version up to 5.3.0: fixed in 5.3.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 39× 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 241 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 141 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-4372?
CVE-2026-4372 is a high-severity vulnerability; its CVE record was published on May 24, 2026. A critical remote code execution vulnerability exists in all versions of the HuggingFace transformers library prior to version 5.3.0. The vulnerability allows an attacker to craft a malicious config.json file containing the _attn_implementation_internal field set to an attacker-controlled…
When was the CVE record for CVE-2026-4372 published?
The CVE record for CVE-2026-4372 was published on May 24, 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 July 23, 2026; the record at its source may have been updated since.
Is CVE-2026-4372 actively exploited?
CVE-2026-4372 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-4372?
CVE-2026-4372 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-4372?
A fix for CVE-2026-4372 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-4372 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-4372

Explore →

Is Your Infrastructure Affected by CVE-2026-4372?

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

Book a Demo →Browse All CVEs