Skip to content

Harness Allows Arbitrary File Write in Gitness LFS server

High severity GitHub Reviewed Published Aug 29, 2025 in harness/harness • Updated Aug 29, 2025

Package

gomod github.com/harness/gitness (Go)

Affected versions

>= 1.0.4, < 3.3.0
< 1.0.4-gitspaces-beta.0.20250808064055-21c5ce42ae13

Patched versions

3.3.0
1.0.4-gitspaces-beta.0.20250808064055-21c5ce42ae13

Description

Impact

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.

Patches

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

References

@Sam-Harness Sam-Harness published to harness/harness Aug 29, 2025
Published to the GitHub Advisory Database Aug 29, 2025
Reviewed Aug 29, 2025
Published by the National Vulnerability Database Aug 29, 2025
Last updated Aug 29, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(12th percentile)

Weaknesses

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Learn more on MITRE.

External Control of File Name or Path

The product allows user input to control or influence paths or file names that are used in filesystem operations. Learn more on MITRE.

CVE ID

CVE-2025-58158

GHSA ID

GHSA-w469-hj2f-jpr5

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.