CVE-2025-58158: Harness Affected by Arbitrary File Write in Gitness LFS server
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.
Other sources
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.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-58158?
CVE-2025-58158 is considered a high-severity vulnerability due to its potential impact on file retrieval and upload operations.
How do I fix CVE-2025-58158?
To remediate CVE-2025-58158, upgrade Open Source Harness to version 3.3.0 or later.
What software is affected by CVE-2025-58158?
CVE-2025-58158 affects Open Source Harness versions prior to 3.3.0.
What functionalities are impacted by CVE-2025-58158?
CVE-2025-58158 affects the git LFS server functionality, allowing unauthorized access to file retrieval and uploads.
Is there a workaround for CVE-2025-58158 before upgrading?
Currently, there are no documented workarounds for CVE-2025-58158, and upgrading is the recommended action.