# CVE-2026-103028: SFTPGo source-side file-pattern filter bypass during copy operations

> Authenticated users can bypass file-pattern filters during copy operations to read restricted files or reproduce hidden contents in allowed locations.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-wwv9-g5x4-966q, GO-2026-6802

## What is CVE-2026-103028?

CVE-2026-103028 is a medium-severity missing authorization vulnerability in drakkan sftpgo, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SFTPGo is an open source, event-driven file transfer solution. From 2.5.0 until 2.7.6, an authenticated user with copy permission can copy a source file denied by denied_patterns or outside allowed_patterns to an allowed destination name because file-pattern filters are evaluated only on the destination. The user can then read the denied file contents. Recursive directory copies can reproduce restricted contents under an allowed path, and the hide policy is bypassed because files that appear missing to stat and directory listings can still be copied. Home-directory boundaries, virtual-folder layout, per-directory permissions, access to other accounts, and administrative authorization remain enforced. This issue is fixed in 2.7.6.

Weakness: CWE-863 (Incorrect Authorization)

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

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.5.0 | 2.7.6 |
| `github.com/drakkan/sftpgo/v2` | Go | From 2.5.0 | 2.7.6 |
| `github.com/drakkan/sftpgo/v2` | Go | From 2.5.0 | 2.7.6 |
| `github.com/drakkan/sftpgo` | Go | All versions | None |

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

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

## Is CVE-2026-103028 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103028 is a medium-severity missing authorization vulnerability in drakkan sftpgo, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103028 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/drakkan/sftpgo/v2 (Go): affected from 2.5.0; fixed in 2.7.6
- github.com/drakkan/sftpgo/v2 (Go): affected from 2.5.0; fixed in 2.7.6
- github.com/drakkan/sftpgo/v2 (Go): affected from 2.5.0; fixed in 2.7.6
- 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-103028/ (Markdown: https://insights.sbomify.com/CVE-2026-103028/index.md)
```

## Sources

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

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