Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9

SFTPGo improperly sanitizes placeholders in group home directories/key prefixes

CVE-2026-30915GHSA-m83q-5wr4-4gfp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/drakkan/sftpgo/v2 2.7.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-30915: 0.33% estimated exploitation activity in the next 30 days; percentile 26.04 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-m83q-5wr4-4gfp

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-30915

Advisory: SFTPGo improperly sanitizes placeholders in group home directories/key prefixes
IDs: CVE-2026-30915, GHSA-m83q-5wr4-4gfp
Record: https://patchnext.com/advisories/cve-2026-30915 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/drakkan/sftpgo/v2 2.7.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/drakkan/sftpgo/v2: affected >= 2.3.0, <= 2.7.0; fixed in 2.7.1

## Suggested inspection (read-only)
- Go github.com/drakkan/sftpgo/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/drakkan/sftpgo/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-m83q-5wr4-4gfp (GitHub-reviewed advisory GHSA-m83q-5wr4-4gfp lists affected ranges: Go github.com/drakkan/sftpgo/v2 >=2.3.0 <=2.7.0)

Commands are suggestions: review each one before running it.

Loading voting…