CVE-2025-58158

Harness Allows Arbitrary File Write in Gitness LFS server

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.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2025-58158 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.3.0, 1.0.4-gitspaces-beta.0.20250808064055-21c5ce42ae13); upgrading removes the vulnerable code path.

Kodem intelligence

Users have to upgrade to v3.3.0 . All previous versions are affected by this vulnerability.

1. What is CVE-2025-58158? CVE-2025-58158 is a high-severity path traversal vulnerability in github.com/harness/gitness (go), affecting versions >= 1.0.4, < 3.3.0. It is fixed in 3.3.0, 1.0.4-gitspaces-beta.0.20250808064055-21c5ce42ae13. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2025-58158? CVE-2025-58158 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/harness/gitness are affected by CVE-2025-58158? github.com/harness/gitness (go) versions >= 1.0.4, < 3.3.0 is affected.
4. Is there a fix for CVE-2025-58158? Yes. CVE-2025-58158 is fixed in 3.3.0, 1.0.4-gitspaces-beta.0.20250808064055-21c5ce42ae13. Upgrade to this version or later.
5. Is CVE-2025-58158 exploitable, and should I be worried? Whether CVE-2025-58158 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-58158 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-58158?
   • Upgrade github.com/harness/gitness to 3.3.0 or later
   • Upgrade github.com/harness/gitness to 1.0.4-gitspaces-beta.0.20250808064055-21c5ce42ae13 or later