Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.3amended

SFTPGo source-side file-pattern filter bypass during copy operations

CVE-2026-103028GHSA-wwv9-g5x4-966q

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

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

  • Go github.com/drakkan/sftpgo/v2

    Affected
    >= 2.5.0, <= 2.7.5
    Fixed in
    2.7.6

  • Go github.com/drakkan/sftpgo

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-103028: 0.22% estimated exploitation activity in the next 30 days; percentile 12.46 (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.

Summary File pattern filters (deniedpatterns / allowedpatterns) were evaluated on the destination of a copy only. A user holding the copy permission could copy a file denied by the filters to a permitted name and then read it. A recursive directory copy reproduced the contents of a restricted directory under a path where the filters do not deny them, and the hide policy was affected in the same way: a file reported as missing by stat and by directory listings could still be copied. Details An authenticated user can read the contents of files that the file pattern filters are configured to deny them. Nothing else is bypassed: the home directory, the virtual folder layout and the per-directory permissions are all still enforced, and both ends of the copy are paths the account can already reach. No access to other accounts and no administrative capability.

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

    Amended from ghsa record GHSA-wwv9-g5x4-966q

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6802

  3. Revision 1 · created ·

    Published from osv record GHSA-wwv9-g5x4-966q

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-103028

Advisory: SFTPGo source-side file-pattern filter bypass during copy operations
IDs: CVE-2026-103028, GHSA-wwv9-g5x4-966q
Record: https://patchnext.com/advisories/cve-2026-103028 (revision 3, source checked 26 Oct 2026, 15:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/drakkan/sftpgo/v2 2.7.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/drakkan/sftpgo/v2: affected >= 2.5.0, <= 2.7.5; fixed in 2.7.6
- Go github.com/drakkan/sftpgo: affected every version

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/drakkan/sftpgo/v2, github.com/drakkan/sftpgo.
- 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://osv.dev/vulnerability/GO-2026-6802 (OSV record GO-2026-6802 lists affected ranges: Go github.com/drakkan/sftpgo >=0; Go github.com/drakkan/sftpgo/v2 >=2.5.0 <2.7.6 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-wwv9-g5x4-966q (OSV record GHSA-wwv9-g5x4-966q lists affected ranges: Go github.com/drakkan/sftpgo/v2 >=2.5.0 <2.7.6 (fixed))
- Verified: https://github.com/advisories/GHSA-wwv9-g5x4-966q (GitHub-reviewed advisory GHSA-wwv9-g5x4-966q lists affected ranges: Go github.com/drakkan/sftpgo/v2 >=2.5.0 <=2.7.5)

Commands are suggestions: review each one before running it.

Loading voting…