Quick answers
- Is CVE-2026-103028 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103028 being exploited in the wild.
- How severe is CVE-2026-103028?
- Medium severity, with a CVSS score of 4.3, published 13 October 2026.
- Which products and versions are affected?
- Drakkan SFTPGo 2.5.0 through 2.7.5; github.com/drakkan/sftpgo (Go) SEMVER:introduced=0; github.com/drakkan/sftpgo/v2 (Go) >= 2.5.0, <= 2.7.5, SEMVER:introduced=2.5.0,fixed=2.7.6.
- Is there a fix for CVE-2026-103028?
- Yes. github.com/drakkan/sftpgo/v2 (Go): upgrade to 2.7.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-103028 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-103028?
- Check whether you run Drakkan SFTPGo, github.com/drakkan/sftpgo (Go) or github.com/drakkan/sftpgo/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/drakkan/sftpgo/v2 (Go): upgrade to 2.7.6 or later
go get github.com/drakkan/sftpgo/v2@v2.7.6
Technical details
The vulnerability is an incorrect authorization check (CWE-863) where file pattern filters are evaluated only on the copy destination, not the source. An authenticated user with copy permissions can exploit this by copying files matching denied_patterns to names matching allowed_patterns, then reading the copied content. The attack requires existing authentication and access to both source and destination paths; no other access controls or administrative capabilities are bypassed.
Affected products
- drakkan SFTPGo 2.5.0 through 2.7.5
Identifiers
- CVE-2026-103028
- GHSA-wwv9-g5x4-966q
- GO-2026-6802
Timeline
- 2026-09-19: disclosed
- 2026-10-15: advisory
- 2026-10-15: patched: Version 2.7.6 released