# SFTPGo improperly sanitizes placeholders in group home directories/key prefixes

Advisory record · `GHSA-m83q-5wr4-4gfp`

- **Identifiers:** `GHSA-m83q-5wr4-4gfp` · `CVE-2026-30915` · `GO-2026-4697`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Published:** 13 Mar 2026
- **Updated:** 24 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 Mar 2026, 18:56 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/drakkan/sftpgo/v2` (Go): affected `>=2.3.0, <2.7.1`; fixed in `2.7.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> SFTPGo versions from 2.3.0 before 2.7.1 mishandle placeholders such as %username% in group home directories and key prefixes, so the substituted value is not fully sanitized against relative path components. An attacker who can create a user with a specially crafted username may cause the resulting path to resolve to a parent directory rather than the intended subdirectory. Upgrade to SFTPGo 2.7.1 or later. The source gives few details on the exact access an attacker needs.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0035, the 28th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:08 UTC: First seen by agentprime
- 31 Oct 2026, 15:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m83q-5wr4-4gfp)

## Sources

- [GitHub Advisory Database: GHSA-m83q-5wr4-4gfp](https://github.com/advisories/GHSA-m83q-5wr4-4gfp)
- [OSV: GHSA-m83q-5wr4-4gfp](https://osv.dev/vulnerability/GHSA-m83q-5wr4-4gfp)
- <https://github.com/drakkan/sftpgo/security/advisories/GHSA-m83q-5wr4-4gfp>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-30915>
- <https://github.com/drakkan/sftpgo>
- <https://pkg.go.dev/vuln/GO-2026-4697>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-m83q-5wr4-4gfp>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m83q-5wr4-4gfp/>. Everything for agents: <https://agentprime.io/llms.txt>.
