Arbitrary file write via unchecked LFS object ID
Published Aug 29, 2025 · Updated Aug 29, 2025
Path traversal in Harness Open Source Gitness before 3.3.0 allows remote authenticated users to write files outside LFS storage. The Upload controller passes a client-supplied LFS object ID into getLFSObjectPath and writes the request body without verifying that its SHA-256 hash matches the ID. Git LFS must be in use and the attacker must have API access; a crafted upload can replace any file writable by the service account and compromise the server.
Summary
What happened
Path traversal in Harness Open Source Gitness before 3.3.0 allows remote authenticated users to write files outside LFS storage. The Upload controller passes a client-supplied LFS object ID into getLFSObjectPath and writes the request body without verifying that its SHA-256 hash matches the ID. Git LFS must be in use and the attacker must have API access; a crafted upload can replace any file writable by the service account and compromise the server.
The record
- CVE
- CVE-2025-58158
- Published
- Aug 29, 2025
- Updated
- Aug 29, 2025
- Vendor
- Harness
- Product
- Harness
- Classifications
- CWE-22, CWE-73, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 29, 2025CVE publishedPublication date reported by the CVE source.
- Aug 29, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo