CVE-2026-30915: SFTPGo improperly sanitizes placeholders in group home directories/key prefixes
Impact
SFTPGo versions before v2.7.1 contain an input validation issue in the handling of dynamic group paths, for example, home directories or key prefixes.
When a group is configured with a dynamic home directory or key prefix using placeholders like %username%, the value replacing the placeholder is not strictly sanitized against relative path components. Consequently, if a user is created with a specially crafted username the resulting path may resolve to a parent directory instead of the intended sub-directory.
Patches
This issue is fixed in version v2.7.1
Other sources
SFTPGo is an open source, event-driven file transfer solution. SFTPGo versions before v2.7.1 contain an input validation issue in the handling of dynamic group paths, for example, home directories or key prefixes. When a group is configured with a dynamic home directory or key prefix using placeholders like %username%, the value replacing the placeholder is not strictly sanitized against relative path components. Consequently, if a user is created with a specially crafted username the resulting path may resolve to a parent directory instead of the intended sub-directory. This issue is fixed in version v2.7.1
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-30915?
CVE-2026-30915 is considered a high severity vulnerability due to improper input validation of dynamic group paths.
How do I fix CVE-2026-30915?
To mitigate CVE-2026-30915, update SFTPGo to version 2.7.1 or later where the input validation issue has been addressed.
What are the affected versions for CVE-2026-30915?
CVE-2026-30915 affects SFTPGo versions from 2.3.0 to 2.7.0.
What kind of issue is CVE-2026-30915?
CVE-2026-30915 is an input validation issue related to the handling of dynamic group home directories.
Who is affected by CVE-2026-30915?
Any user or organization using vulnerable versions of SFTPGo for managing group directories is at risk from CVE-2026-30915.