CVE-2024-37032

HIGHNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 94% probability of exploitation within the next 30 days (top 0.1% of all CVEs). NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
8.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 90%
CISA-KEV: Not listedEPSS: 90%CVSS: 8.8Exploit: NoneExposed: 0

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

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.0(high)
EPSS
99.8%
KEV
Not listed

Published

May 31, 2024

Last Modified

May 1, 2025

References (8)

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/ollama/ollama—0.1.34—

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-07-15 01:59 UTCEPSS rescore
  2. 2026-07-15 01:59 UTCEPSS rescore
  3. 2026-07-14 07:40 UTCOSV refresh
  4. 2026-07-08 15:14 UTCEPSS rescore
  5. 2026-07-08 15:13 UTCEPSS rescore
  6. 2026-07-01 15:05 UTCEPSS rescore
  7. 2026-06-27 03:07 UTCEPSS rescore
  8. 2026-06-27 03:07 UTCEPSS rescore
  9. 2026-06-26 05:16 UTCOSV refresh
  10. 2026-06-24 14:04 UTCEPSS rescore
  11. 2026-06-24 14:04 UTCEPSS rescore
  12. 2026-06-23 21:32 UTCEPSS rescore
  13. 2026-06-23 21:32 UTCEPSS rescore
  14. 2026-06-22 14:25 UTCEPSS rescore
  15. 2026-06-22 14:25 UTCEPSS rescore
  16. 2026-06-16 17:52 UTCEPSS rescore
  17. 2026-06-16 17:52 UTCEPSS rescore
  18. 2026-06-15 17:47 UTCEPSS rescore
  19. 2026-06-12 23:11 UTCEPSS rescore
  20. 2026-06-10 13:21 UTCEPSS rescore
  21. 2026-06-08 16:11 UTCOSV refresh
  22. 2026-06-08 14:16 UTCEPSS rescore
  23. 2026-06-05 06:09 UTCEPSS rescore
  24. 2026-06-05 06:09 UTCEPSS rescore
  25. 2026-06-02 20:12 UTCEPSS rescore
Show 8 more
  1. 2026-06-01 13:51 UTCEPSS rescore
  2. 2026-06-01 13:51 UTCEPSS rescore
  3. 2026-05-31 22:30 UTCEPSS rescore
  4. 2026-05-31 22:30 UTCEPSS rescore
  5. 2026-05-26 07:18 UTCEPSS rescore
  6. 2026-05-26 07:18 UTCEPSS rescore
  7. 2026-05-26 07:18 UTCEPSS rescore
  8. 2026-05-24 00:44 UTCEG score recompute

Publicly available exploits

(5 references)

Working exploit code is in the public domain (1 Metasploit module) (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCitzSh4dowxZ/CVE-2024-37032-PoC
    First seen 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
    First seen Oct 21, 2024

    CVE-2024-45436

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

    Path traversal in Ollama with rogue registry server

    Open source ↗
  • Metasploitexploit/linux/http/ollama_rce_cve_2024_37032✓ verified
    First seen May 5, 2024

    Ollama Model Registry Path Traversal RCE

    Open source ↗
  • Nucleihttp/cves/2024/CVE-2024-37032.yaml
    First seen Jan 1, 2024

    Ollama - Remote Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-37032?
CVE-2024-37032 is a high vulnerability 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 CVE-2024-37032 disclosed?
CVE-2024-37032 was first published in the National Vulnerability Database on May 31, 2024, with the most recent update on May 1, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-37032 actively exploited?
CVE-2024-37032 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.
How do I remediate CVE-2024-37032?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-37032, 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-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.

Start Free Scan →Browse All CVEs