How severe is GHSA-8hqg-whrw-pv92?

No CVSS score has been assigned to GHSA-8hqg-whrw-pv92 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8hqg-whrw-pv92?

GHSA-8hqg-whrw-pv92 affects the following packages: github.com/ollama/ollama (Go). Ecosystems affected: Go.

How do I fix GHSA-8hqg-whrw-pv92?

Update github.com/ollama/ollama to 0.1.34 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8hqg-whrw-pv92 is resolved across your whole dependency graph.

How do I detect GHSA-8hqg-whrw-pv92 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ollama/ollama, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-8hqg-whrw-pv92 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-8hqg-whrw-pv92 actively exploited in the wild?

Yes. There are 4 known exploit references for GHSA-8hqg-whrw-pv92, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-8hqg-whrw-pv92?

GHSA-8hqg-whrw-pv92 has an EPSS (Exploit Prediction Scoring System) score of 89.6%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-8hqg-whrw-pv92?

GHSA-8hqg-whrw-pv92 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-8hqg-whrw-pv92?

A Nuclei detection template exists for GHSA-8hqg-whrw-pv92, meaning automated scanners can fingerprint it. 2 Metasploit modules reference GHSA-8hqg-whrw-pv92, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-8hqg-whrw-pv92 published, and has it been updated?

GHSA-8hqg-whrw-pv92 was published on May 31, 2024 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Ollama does not validate the format of the digest (sha256 with 64 hex digits)GHSA-8hqg-whrw-pv92

Fix: ollama/ollama#4175

GHSA-8hqg-whrw-pv92 is a Path Traversal vulnerability in github.com/ollama/ollama. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for github.com/ollama/ollama — see the affected versions and patch details below.

Also known asCVE-2024-37032GO-2024-2901

Published

May 31, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-8hqg-whrw-pv92.

EPSS Exploitation Probability

via FIRST.org ↗

89.6%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/ollama/ollama

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/ollama/ollama`	all versions	0.1.34`go get github.com/ollama/ollama@v0.1.34`

Affected Products

1 product · 1 configurations

Application

ollamaollama

< 0.1.34

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Ollama before 0.1.34 does not validate the format of the digest (sha256 …

github.comGithubJun 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ollama/ollama, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/ollama/ollama to 0.1.34 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8hqg-whrw-pv92 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

How to detect GHSA-8hqg-whrw-pv92

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-8hqg-whrw-pv92 -u https://target

Template: Ollama - Remote Code Execution
Severity: critical
Impact: Attackers can exploit improper digest validation to achieve remote code execution on Ollama servers.
Remediation: Update Ollama to version 0.1.34 or later.

Template by ProjectDiscovery nuclei-templates (kaks3c), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-8hqg-whrw-pv92 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works