CVE-2024-37032

CRITICALNVD 8.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because EPSS predicted 90% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekWeaponized
9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 90%
  • Public exploit code is available (Metasploit, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 90%CVSS: 8.8Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is available — apply it.

Ollama before 0.1.34 does not validate the format of the digest (sha256 with 64 hex digits) when getting the model path, and thus mishandles the TestGetBlobsPath test cases such as fewer than 64 hex digits, more than 64 hex digits, or an initial ../ substring.

CVSS v3
8.8
EG Score
9.0CRITICALhigh confidence
EG Risk
76
EG Risk 76/100

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 (value × EchelonGraph’s weight)
Severity90% × 45%
The EG Score, 9.0 of 10.
Exploitation90% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
90%
EPSS %ILE
99th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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 31, 2024

Last Modified

May 1, 2025

Advisory Details (4)

Auto-updated Aug 24, 2026
Patch available. Sources: github_pr.
Web page

Probllama in Ollama: A tale of a yet another RCE vulnerability (CVE-2024-37032) - vsociety

https://www.vicarius.io/vsociety/posts/probllama-in-ollama-a-tale-of-a-yet-another-rce-vulnerability-cve-2024-37032
GitHub pull request

validate the format of the digest when getting the model path

Fix merged in ollama/ollama PR #4175 on 2024-05-05 — awaiting tagged release

https://github.com/ollama/ollama/pull/4175
Web page

Comparing v0.1.33...v0.1.34 · ollama/ollama · GitHub

https://github.com/ollama/ollama/compare/v0.1.33...v0.1.34
Web page

ollama/server/modelpath_test.go at adeb40eaf29039b8964425f69a9315f9f1694ba8 · ollama/ollama · GitHub

https://github.com/ollama/ollama/blob/adeb40eaf29039b8964425f69a9315f9f1694ba8/server/modelpath_test.go#L41-L58

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/ollama/ollama—
  • every version up to 0.1.34: fixed in 0.1.34
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 18× 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.

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. 17 repeat rows among the latest 79 are merged into the row they repeat.

  1. 2026-10-12 17:51 UTCEG score recompute
  2. 2026-10-12 14:09 UTCEG score recompute
  3. 2026-10-11 21:16 UTCEG score recompute
  4. 2026-10-11 16:09 UTCEG score recompute
  5. 2026-10-10 20:33 UTCOSV refresh
  6. 2026-10-07 23:46 UTCEPSS rescoreEPSS 90% · 99th percentile
  7. 2026-10-05 17:41 UTCEPSS rescoreEPSS 90% · 99th percentile
  8. 2026-09-30 19:47 UTCEG score recompute
  9. 2026-09-30 15:01 UTCEPSS rescoreEPSS 90% · 99th percentile
  10. 2026-09-29 15:17 UTCEPSS rescoreEPSS 90% · 99th percentile
  11. 2026-09-28 13:49 UTCEPSS rescoreEPSS 90% · 99th percentile
  12. 2026-09-24 14:01 UTCEPSS rescoreEPSS 90% · 99th percentile
  13. 2026-09-22 14:46 UTCEPSS rescoreEPSS 90% · 99th percentile
  14. 2026-09-21 20:32 UTCEPSS rescoreEPSS 90% · 99th percentile
  15. 2026-09-21 08:19 UTCOSV refresh
  16. 2026-09-20 20:14 UTCEPSS rescoreEPSS 90% · 99th percentile
  17. 2026-09-19 15:40 UTCEPSS rescoreEPSS 90% · 99th percentile
  18. 2026-09-16 14:06 UTCEPSS rescoreEPSS 90% · 99th percentile
  19. 2026-09-12 14:59 UTCEPSS rescoreEPSS 90% · 99th percentile
  20. 2026-09-08 21:58 UTCEPSS rescoreEPSS 90% · 99th percentile
  21. 2026-09-06 13:46 UTCEPSS rescoreEPSS 90% · 99th percentile
  22. 2026-09-05 15:26 UTCEPSS rescoreEPSS 90% · 99th percentile
  23. 2026-09-02 05:44 UTCOSV refresh
  24. 2026-08-30 19:15 UTCEPSS rescoreEPSS 90% · 99th percentile
  25. 2026-08-30 01:20 UTCEPSS rescoreEPSS 90% · 99th percentile
Show 37 more
  1. 2026-08-28 21:39 UTCEPSS rescoreEPSS 90% · 99th percentile
  2. 2026-08-25 13:47 UTCEPSS rescoreEPSS 90% · 99th percentile
  3. 2026-08-24 14:15 UTCEPSS rescoreEPSS 90% · 99th percentile
  4. 2026-08-21 23:47 UTCEPSS rescoreEPSS 90% · 99th percentile
  5. 2026-08-16 06:59 UTCOSV refresh
  6. 2026-08-12 13:49 UTCEPSS rescoreEPSS 90% · 99th percentile
  7. 2026-08-10 23:58 UTCEPSS rescoreEPSS 90% · 99th percentile
  8. 2026-08-08 16:35 UTCEPSS rescoreEPSS 90% · 99th percentile
  9. 2026-08-05 19:16 UTCEPSS rescoreEPSS 90% · 99th percentile
  10. 2026-08-01 00:42 UTCOSV refresh
  11. 2026-07-30 16:26 UTCEPSS rescoreEPSS 90% · 99th percentile
  12. 2026-07-27 14:11 UTCEPSS rescoreEPSS 90% · 99th percentile
  13. 2026-07-24 14:16 UTCEPSS rescoreEPSS 90% · 99th percentile
  14. 2026-07-23 02:38 UTCEG score recompute
  15. 2026-07-22 14:07 UTCEPSS rescoreEPSS 90% · 99th percentile
  16. 2026-07-15 16:56 UTCEPSS rescoreEPSS 90% · 99th percentile
  17. 2026-07-15 01:59 UTCEPSS rescoreEPSS 90% · 99th percentile
  18. 2026-07-14 07:40 UTCOSV refresh
  19. 2026-07-08 15:13 UTCEPSS rescoreEPSS 90% · 99th percentile
  20. 2026-07-01 15:05 UTCEPSS rescoreEPSS 90% · 99th percentile
  21. 2026-06-27 03:07 UTCEPSS rescoreEPSS 90% · 99th percentile
  22. 2026-06-26 05:16 UTCOSV refresh
  23. 2026-06-24 14:04 UTCEPSS rescoreEPSS 90% · 99th percentile
  24. 2026-06-23 21:32 UTCEPSS rescoreEPSS 90% · 99th percentile
  25. 2026-06-22 14:25 UTCEPSS rescoreEPSS 90% · 99th percentile
  26. 2026-06-16 17:52 UTCEPSS rescoreEPSS 89% · 99th percentile
  27. 2026-06-15 17:47 UTCEPSS rescoreEPSS 89% · 99th percentile
  28. 2026-06-12 23:11 UTCEPSS rescoreEPSS 94% · 99th percentile
  29. 2026-06-10 13:21 UTCEPSS rescoreEPSS 94% · 99th percentile
  30. 2026-06-08 16:11 UTCOSV refresh
  31. 2026-06-08 14:16 UTCEPSS rescoreEPSS 94% · 99th percentile
  32. 2026-06-05 06:09 UTCEPSS rescoreEPSS 94% · 99th percentile
  33. 2026-06-02 20:12 UTCEPSS rescoreEPSS 94% · 99th percentile
  34. 2026-06-01 13:51 UTCEPSS rescoreEPSS 94% · 99th percentile
  35. 2026-05-31 22:30 UTCEPSS rescoreEPSS 94% · 99th percentile
  36. 2026-05-26 07:18 UTCEPSS rescoreEPSS 94% · 99th percentile
  37. 2026-05-24 00:44 UTCEG score recompute

Publicly available exploits

(5 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 3 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Metasploitexploit/linux/http/ollama_rce_cve_2024_37032✓ verified
    Published Feb 25, 2026

    Ollama Model Registry Path Traversal RCE

    Open source ↗
  • GitHub PoCitzSh4dowxZ/CVE-2024-37032-PoC
    Published May 19, 2026

    PoC for CVE-2024-37032 (Probllama): Ollama <=0.1.33 path traversal/arbitrary file write via model digest handling, using a FastAPI rogue registry, connector workflow, and shared object preload demo for authorized lab testing.

    Open source ↗
  • GitHub PoCpankass/CVE-2024-37032_CVE-2024-45436
    Published Oct 21, 2024

    CVE-2024-45436

    Open source ↗
  • Nucleihttp/cves/2024/CVE-2024-37032.yaml
    Published Jul 9, 2024

    Ollama - Remote Code Execution

    Open source ↗
  • GitHub PoCBi0x/CVE-2024-37032
    Published Jun 26, 2024

    Path traversal in Ollama with rogue registry server

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-37032?
CVE-2024-37032 is a critical-severity vulnerability; its CVE record was published on May 31, 2024. Ollama before 0.1.34 does not validate the format of the digest (sha256 with 64 hex digits) when getting the model path, and thus mishandles the TestGetBlobsPath test cases such as fewer than 64 hex digits, more than 64 hex digits, or an initial ../ substring.
When was the CVE record for CVE-2024-37032 published?
The CVE record for CVE-2024-37032 was published on May 31, 2024. 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 May 1, 2025; the record at its source may have been updated since.
Is CVE-2024-37032 actively exploited?
CVE-2024-37032 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 90% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-37032?
CVE-2024-37032 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2024-37032?
A fix for CVE-2024-37032 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-37032

Explore →

Is Your Infrastructure Affected by CVE-2024-37032?

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

Book a Demo →Browse All CVEs