CVE-2026-5241

CRITICALNVD 9.69.6
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.6 under NVD CVSS v3. EPSS exploit probability: 0.9% (60th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.0 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-06-03) is not newer than that change (2026-09-01), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — Patch released this weekElevated
9.6EG
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.9%CVSS: 9.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

A vulnerability in the LightGlue model loading path of huggingface/transformers version 5.2.0 allows an attacker-controlled model repository to execute arbitrary code during model initialization. The issue arises because the trust_remote_code parameter, intended to prevent remote code execution, is overridden by untrusted serialized configuration data in a nested code path. Specifically, when loading a LightGlue model using AutoModel.from_pretrained() with trust_remote_code=False, the LightGlueConfig reads the trust_remote_code value from the untrusted config.json file and propagates it into nested AutoConfig.from_pretrained() calls. This results in the execution of attacker-provided Python modules, even when the victim explicitly disables remote code execution. The vulnerability poses a high risk for environments such as API inference servers, research notebooks, CI/CD pipelines, and model evaluation workers, potentially leading to credential theft, lateral movement, or persistence/backdoor deployment.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 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.9%
EPSS %ILE
60th
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 (9.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 CRITICALCVSS-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.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). 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: 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.

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

June 3, 2026

Last Modified

September 1, 2026

Advisory Details (9)

Auto-updated Oct 7, 2026
Patch available. Sources: github_commit.
GitHub commit

commit 676559d5022b (huggingface/transformers)

Fix landed in huggingface/transformers commit 676559d5022b — awaiting tagged release

https://github.com/huggingface/transformers/commit/676559d5022b74aaa0cee1cee0842b7f27c5320e
Web page

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

https://huntr.com/bounties/ceb3ce1a-4c45-497a-b25e-cb9a7685e619
Red Hat

2484384 – (CVE-2026-5241) CVE-2026-5241 python-transformers: python-transformers: Arbitrary code execution due to overridden trust_remote_code setting

https://bugzilla.redhat.com/show_bug.cgi?id=2484384
Red HatMentions a patch (unverified)

CVE-2026-5241 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-5241
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:60520
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:42644
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:37275
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:34456

Patch Availability(15)

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
transformers0.1 ... 5.2.0 (212 versions)
  • every version up to 5.5.0: fixed in 5.5.0
  • every version through 5.2.0: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-5241?
CVE-2026-5241 is a critical-severity vulnerability; its CVE record was published on June 3, 2026. A vulnerability in the LightGlue model loading path of huggingface/transformers version 5.2.0 allows an attacker-controlled model repository to execute arbitrary code during model initialization. The issue arises because the trustremotecode parameter, intended to prevent remote code execution, is…
When was the CVE record for CVE-2026-5241 published?
The CVE record for CVE-2026-5241 was published on June 3, 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 1, 2026; the record at its source may have been updated since.
Is CVE-2026-5241 actively exploited?
CVE-2026-5241 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (60th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-5241?
CVE-2026-5241 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-5241?
A fix for CVE-2026-5241 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-5241 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-5241

Explore →

Is Your Infrastructure Affected by CVE-2026-5241?

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