CVE-2024-37032: 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
Noroxi assessment
Priority: This week (action score 62/100)
- A ready-made attack module is public (Metasploit, Nuclei); exploiting it takes no special expertise.
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 89.6% (FIRST EPSS); higher than 99.7% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: github.com/ollama/ollama (Go) 0.1.34; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20241213T205935-1.1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Don’t wait for the next maintenance window. Upgrade to github.com/ollama/ollama (Go) 0.1.34; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20241213T205935-1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 31, 2024
- Updated
- Jun 17, 2026
- EPSS
- 89.6% · 99th percentile
- CWE
- CWE-22
Report tools
Action score
62
This week
Don’t wait for the next maintenance window.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 27 / 30 · 89.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Weaponized exploit exists
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| ollama | ollama | cpe:2.3:a:ollama:ollama |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ollama ollamabefore 0.1.34
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/ollama/ollama | before 0.1.34 | 0.1.34 |
| openSUSE:Tumbleweed | govulncheck-vulndb | before 0.0.20241213T205935-1.1 | 0.0.20241213T205935-1.1 |
Same product
ollama: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-42249Remote Code Execution in Ollama via Update Mechanism40Plan
- CVE-2026-42248Missing Signature Verification for Updates in Ollama40Plan
- CVE-2025-63389A critical authentication bypass vulnerability exists in Ollama platform's API endpoints in versions prior to and including v0.12.3.39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-28224Apr 8, 2024 · Ollama before 0.1.29 has a DNS rebinding vulnerability that can inadvertently allow remote access to the full API, thereby letting an unauth26Monitor
- Later →CVE-2024-45436Aug 28, 2024 · extractFromZipFile in model.go in Ollama before 0.1.47 can extract members of a ZIP archive outside of the parent directory.31Monitor
- Later →CVE-2024-39719Oct 31, 2024 · An issue was discovered in Ollama through 0.3.14.31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/ollama/ollama | 0.1.34 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20241213T205935-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×4
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Nuclei detection template | Nuclei template CVE-2024-37032 | — |
| Metasploit module | exploit/linux/http/ollama_rce_cve_2024_37032Ollama Model Registry Path Traversal RCEexploit | 2024-05-05 |
| Proof-of-concept repository on GitHub | stars:56 | 2024-06-26 |
| Proof-of-concept repository on GitHub | stars:1 | 2024-07-10 |
| Proof-of-concept repository on GitHub | stars:8 | 2024-10-21 |
| Proof-of-concept repository on GitHub | stars:8 | 2026-05-19 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Metasploit-26 d
- Published
- First PoC+26 d
- TodayNov 6, 2026+890 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-4543689 days apartextractFromZipFile in model.go in Ollama before 0.1.47 can extract members of a ZIP archive outside of the parent directory.31Monitor
- CVE-2024-39722153 days apartAn issue was discovered in Ollama before 0.1.46.31Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0596 · May 31, 2024(Ollama Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.