CVE-2026-30915
Path Traversal in SFTPGo Dynamic Group Paths Allows Directory Escape
Publication date: 2026-03-13
Last updated on: 2026-03-18
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sftpgo_project | sftpgo | From 2.3.0 (inc) to 2.7.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in SFTPGo versions before v2.7.1 and involves improper input validation when handling dynamic group paths such as home directories or key prefixes. Specifically, when placeholders like %username% are used to define these paths, the value replacing the placeholder is not properly sanitized against relative path components. This means that if a user is created with a specially crafted username, the resulting path could point to a parent directory instead of the intended sub-directory.
The issue allows path traversal through crafted usernames, potentially leading to unauthorized access or manipulation of files outside the intended directory structure.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker to bypass intended directory restrictions. By exploiting the input validation flaw with a crafted username, an attacker could cause the system to resolve file paths to parent directories, potentially accessing or modifying files outside their authorized area.
Such unauthorized access could lead to data exposure, data corruption, or other security breaches depending on the files accessible through the path traversal.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade SFTPGo to version v2.7.1 or later, where the input validation issue with dynamic group paths has been fixed.