CVE-2026-5241

CRITICALNVD 9.69.6
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.6 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 54% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 3 sources updated this weekElevated
9.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.6Exploit: Elevated riskExposed: 0

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.6(medium)
EG Risk
59(Track*)
EG Risk 59/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity96% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

June 3, 2026

Last Modified

September 1, 2026

Advisory Details (9)

Auto-updated Sep 3, 2026
Upstream fix merged — awaiting tagged release. 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
generic

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

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

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
redhat Patch Available

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

Patch Availability(4)

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 rangeFixed inDependents
transformers0.1 ... 5.2.0 (212 versions)5.5.0

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 109× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 318 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-5241?
CVE-2026-5241 is a critical vulnerability 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 CVE-2026-5241 disclosed?
CVE-2026-5241 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5241 actively exploited?
CVE-2026-5241 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.7% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5241, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.