dbcve.org
SftpgoApplication · Sftpgo Project

CVE-2026-30914

HIGH · 8.1 CVSS v3.1 Published 2026-03-13
Fix available
A fix is available. Upgrade to 2.7.1 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SFTPGo is an open source, event-driven file transfer solution. In SFTPGo versions prior to 2.7.1, a path normalization discrepancy between the protocol handlers and the internal Virtual Filesystem routing can lead to an authorization bypass. An authenticated attacker can craft specific file paths to bypass folder-level permissions or escape the boundaries of a configured Virtual Folder. This vulnerability is fixed in 2.7.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In SFTPGo versions prior to 2.7.1, a path normalization discrepancy exists between the SFTP/FTP protocol handlers and the internal Virtual Filesystem (VFS) routing. An authenticated attacker can craft specific file paths using path traversal sequences to bypass folder-level permissions and escape the boundaries of their assigned Virtual Folder, gaining unauthorized access to files outside their permitted directory.

MitigationUpgrade SFTPGo to version 2.7.1 or later to obtain the official fix for this authorization bypass vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SftpgoApplication
Affected:< 2.7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SFTPGo version
    Run 'sftpgo --version' or query the /api/version API endpoint if the service is running
    Affected if The installed version is lower than 2.7.1
  2. Locate SFTPGo configuration
    Find the main configuration file (commonly sftpgo.json or in /etc/sftpgo/) and locate the 'virtual_folders' section
    Affected if Virtual folders are defined in the configuration
  3. Verify folder permission bindings
    Examine the virtual_folders array entries and check the 'username' or 'users' fields that bind folder paths to specific users
    Affected if Any virtual folder bindings exist that map paths to users with authenticated access
  4. Review access logs for path traversal
    Inspect SFTP/FTP protocol logs (typically in logs/ subdirectory or via syslog) for requests containing patterns like '../', '..\', or absolute paths from unauthenticated or authenticated users
    Affected if Log entries show path traversal attempts (../ sequences) accessing paths outside assigned virtual folder boundaries

You are affected if SFTPGo version is below 2.7.1 AND virtual folders are configured with user bindings, particularly if logs show path traversal sequences in access attempts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.7.1 or later
Fixed in 2.7.1
Interim mitigation

Upgrade SFTPGo to version 2.7.1 or later to obtain the official fix for this authorization bypass vulnerability.

Recommended fix High confidence

2.7.1

  1. 1. Backup your current SFTPGo configuration and data directory
  2. 2. Download SFTPGo version 2.7.1 from the official GitHub releases page (github.com/nick卓/nick卓/sftpgo)
  3. 3. Stop the currently running SFTPGo service
  4. 4. Replace the existing SFTPGo binary with the new version 2.7.1
  5. 5. Verify the installation by running `sftpgo --version` to confirm version 2.7.1 is installed
  6. 6. Start the SFTPGo service
  7. 7. Verify that virtual folder permissions are working correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sftpgo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30914 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30914 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data