CVE-2025-58158 is a high-severity (CVSS 8.8) Path Traversal vulnerability in github.com/harness/gitness. A fix is available for github.com/harness/gitness — see the affected versions and patch details below.
Harness Affected by Arbitrary File Write in Gitness LFS server
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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 CVE-2025-58158.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/harness/gitness🐹github.com/harness/gitnessReal-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
Harness Open Source is an end-to-end developer platform with Source Control Management, CI/CD Pipelines, Hosted Developer Environments, and Artifact Registries. Prior to version 3.3.0, Open Source Harness git LFS server (Gitness) exposes api to retrieve and upload files via git LFS. Implementation of upload git LFS file api is vulnerable to arbitrary file write. Due to improper sanitization for upload path, a malicious authenticated user who has access to Harness Gitness server api can use a crafted upload request to write arbitrary file to any location on file system, may even compromise the server. Users using git LFS are vulnerable. This issue has been patched in version 3.3.0.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/harness/gitness | ≥ 1.0.4&&< 3.3.0 | 3.3.0go get github.com/harness/gitness@v3.3.0 |
| 🐹Go | github.com/harness/gitness | all versions | 1.0.4-gitspaces-beta.0.20250808064055-21c5ce42ae13go get github.com/harness/gitness@v1.0.4-gitspaces-beta.0.20250808064055-21c5ce42ae13 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/harness/gitness, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/harness/gitness to 3.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-58158 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.
Frequently Asked Questions
Is CVE-2025-58158 in your dependencies?
Find it across Go, including transitive dependencies.