CVE-2026-31237

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-12. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8EG
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.8Exploit: None knownExposed: 0

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

The Ludwig framework thru 0.10.4 is vulnerable to insecure deserialization (CWE-502) through its predict() method. When a user provides a dataset file path to the predict() method, the framework automatically determines the file format. If the file is a pickle (.pkl) file, it is loaded using pandas.read_pickle() without any validation or security restrictions. This allows the deserialization of arbitrary Python objects via the unsafe pickle module. A remote attacker can exploit this by providing a maliciously crafted pickle file, leading to arbitrary code execution on the system running the Ludwig prediction.

CVSS v3
9.8
EG Score
9.8(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
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

May 12, 2026

Last Modified

May 14, 2026

Advisory Details (2)

Auto-updated Sep 9, 2026
No patch confirmed yet.
generic

GitHub - ludwig-ai/ludwig: Low-code framework for building custom LLMs, neural networks, and other AI models · GitHub

https://github.com/ludwig-ai/ludwig
generic

Notion

https://www.notion.so/CVE-2026-31237-35d1e139318881fb95a2ee7c5d0e17d8

Vendor Advisories for CVE-2026-31237(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 / EcosystemFixed in / PatchReleasedSource
pipludwig—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 rangeFixed inDependents
ludwig0.1.0 ... 0.9.3 (56 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 37× 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 349 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31237?
CVE-2026-31237 is a critical vulnerability published on May 12, 2026. The Ludwig framework thru 0.10.4 is vulnerable to insecure deserialization (CWE-502) through its predict() method. When a user provides a dataset file path to the predict() method, the framework automatically determines the file format. If the file is a pickle (.pkl) file, it is loaded using…
When was CVE-2026-31237 disclosed?
CVE-2026-31237 was first published in the National Vulnerability Database on May 12, 2026, with the most recent update on May 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31237 actively exploited?
CVE-2026-31237 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-31237?
CVE-2026-31237 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-31237?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31237, 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-31237

Explore →

Is Your Infrastructure Affected by CVE-2026-31237?

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

Start Free Scan →Browse All CVEs