Path Traversal in github.com/drakkan/sftpgo/v2 (CVE-2026-49244)
Summary
Path traversal in github.com/drakkan/sftpgo/v2 (CVE-2026-49244). Confidential information can be exposed externally. Mitigation: upgrade to 2.7.3 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49244 has been found in github.com/drakkan/sftpgo/v2.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade github.com/drakkan/sftpgo/v2 to 2.7.3 or later.
If unsure, ask your IT team or search "github.com/drakkan/sftpgo/v2 CVE-2026-49244" on the vendor's site.
CVE-2026-49244 (github.com/drakkan/sftpgo/v2) — CWE-22 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.7.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in github.com/drakkan/sftpgo/v2.
Check the vendor advisory for the affected versions of github.com/drakkan/sftpgo/v2.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to 2.7.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/drakkan/sftpgo/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/drakkan/sftpgo/v2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/drakkan/sftpgo/v2を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/drakkan/sftpgo/v2 to 2.7.3ステージング環境で 2.7.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com