github.com/drakkan/sftpgo/v2

CVE-2026-49244

CVE-2026-49244 is a medium-severity path traversal vulnerability in github.com/drakkan/sftpgo/v2 (go), affecting versions >= 2.2.0, <= 2.7.1. It is fixed in 2.7.3.

Key facts
CVSS score
5.9
Medium
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
github.com/drakkan/sftpgo/v2
Fixed in
2.7.3
Disclosed
2026

Summary

Summary The public web-client endpoint for partial ZIP downloads of a browsable share did not correctly confine the client-supplied files entries to the shared directory. A requester able to reach a public share could read files located outside the shared directory, as long as the target's canonical path begins with the shared directory's name. Patches Fixed in v2.7.3. The fix replaces the raw prefix check with a directory-boundary–aware check.

Impact

What is path traversal?

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

Severity and exposure

CVE-2026-49244 has a CVSS score of 5.9 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (2.7.3). Upgrading removes the vulnerable code path.

Affected versions

go

  • github.com/drakkan/sftpgo/v2 (>= 2.2.0, <= 2.7.1)

Security releases

  • github.com/drakkan/sftpgo/v2 → 2.7.3 (go)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-49244 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-49244 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-49244 in your environment

Remediation advice

Upgrade github.com/drakkan/sftpgo/v2 to 2.7.3 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-49244

What is CVE-2026-49244?

CVE-2026-49244 is a medium-severity path traversal vulnerability in github.com/drakkan/sftpgo/v2 (go), affecting versions >= 2.2.0, <= 2.7.1. It is fixed in 2.7.3. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.

How severe is CVE-2026-49244?

CVE-2026-49244 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/drakkan/sftpgo/v2 are affected by CVE-2026-49244?

github.com/drakkan/sftpgo/v2 (go) versions >= 2.2.0, <= 2.7.1 is affected.

Is there a fix for CVE-2026-49244?

Yes. CVE-2026-49244 is fixed in 2.7.3. Upgrade to this version or later.

Is CVE-2026-49244 exploitable, and should I be worried?

Whether CVE-2026-49244 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-49244 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-49244?

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

Stop the waste.
Protect your environment with Kodem.