# CVE-2026-49244: SFTPGo: Path confinement bypass in public browsable share partial ZIP download

> An unauthenticated attacker can bypass path confinement in public browsable shares to read files outside the shared directory via partial ZIP downloads.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-h64p-8h4r-6gfh, GO-2026-5902

## What is CVE-2026-49244?

CVE-2026-49244 is a medium-severity path traversal vulnerability in drakkan sftpgo, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SFTPGo is an open source, event-driven file transfer solution. From 2.2.0 until 2.7.3, the public web-client partial ZIP download endpoint for a browsable share validates client-supplied files entries with a raw byte-prefix comparison rather than a directory-boundary-aware check. An unauthenticated requester who can reach a public share can select a canonical path outside the shared directory when the target path begins with the shared directory's name, such as a sibling path that shares the same prefix. The endpoint then includes the out-of-scope file in the generated download, disclosing its contents. This issue is fixed in version 2.7.3.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-49244?

4 open source packages ship an affected version, including github.com/drakkan/sftpgo/v2 and github.com/drakkan/sftpgo.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/drakkan/sftpgo/v2` | Go | From 2.2.0 | 2.7.3 |
| `github.com/drakkan/sftpgo/v2` | Go | From 2.2.0 | 2.7.3 |
| `github.com/drakkan/sftpgo/v2` | Go | From 2.2.0 | 2.7.3 |
| `github.com/drakkan/sftpgo` | Go | All versions | None |

## How do I fix CVE-2026-49244?

Upgrade github.com/drakkan/sftpgo/v2 to 2.7.3 or later.

## Is CVE-2026-49244 being exploited?

There is no known exploitation of CVE-2026-49244 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49244 and fix it if it is affected.

What it is: CVE-2026-49244 is a medium-severity path traversal vulnerability in drakkan sftpgo, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49244 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/drakkan/sftpgo/v2 (Go): affected from 2.2.0; fixed in 2.7.3
- github.com/drakkan/sftpgo/v2 (Go): affected from 2.2.0; fixed in 2.7.3
- github.com/drakkan/sftpgo/v2 (Go): affected from 2.2.0; fixed in 2.7.3
- github.com/drakkan/sftpgo (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49244/ (Markdown: https://insights.sbomify.com/CVE-2026-49244/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49244
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49244
- OSV: https://osv.dev/vulnerability/CVE-2026-49244

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49244/
Summaries are generated and may contain mistakes; the official description above is the record.