CVE-2026-49245 is a low-severity cross-site scripting (XSS) vulnerability in github.com/drakkan/sftpgo/v2 (go), affecting versions >= 2.2.0, <= 2.7.1. It is fixed in 2.7.3.
Summary The inline query parameter on the browsable-share file download and on the authenticated user file download suppressed Content-Disposition: attachment, so an HTML file stored in a share or home directory could be served as text/html and execute in SFTPGo's web origin (stored XSS). Impact Low. Exploitation requires the attacker to place the file and a victim to open the crafted link, a URL the WebClient never generates, so it requires social engineering, and the practical conditions are narrow: Session cookies are HttpOnly, so the cookie cannot be read by the injected script. Authenticated shares set their own session cookie, which overwrites the victim's WebClient cookie, no account pivot. The realistic case is a public share, or a folder shared between distinct users combined with targeted social engineering. It is a genuine trust-boundary violation (SFTPGo emits attacker-controlled content as active HTML in its own origin), hence an advisory, but the constrained preconditions and the HttpOnly mitigation keep it Low. Patches Upgrade to v2.7.3. These endpoints now always respond with Content-Disposition: attachment; the inline parameter has been removed. See the fix commit for the full technical rationale.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
CVE-2026-49245 has a CVSS score of 3.7 (Low). The vector is network-reachable, low privileges required, and user interaction required. 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.
go
github.com/drakkan/sftpgo/v2 (>= 2.2.0, <= 2.7.1)github.com/drakkan/sftpgo/v2 → 2.7.3 (go)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-49245 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-49245 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-49245 in your environment →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.
CVE-2026-49245 is a low-severity cross-site scripting (XSS) vulnerability in github.com/drakkan/sftpgo/v2 (go), affecting versions >= 2.2.0, <= 2.7.1. It is fixed in 2.7.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
CVE-2026-49245 has a CVSS score of 3.7 (Low). 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.
github.com/drakkan/sftpgo/v2 (go) versions >= 2.2.0, <= 2.7.1 is affected.
Yes. CVE-2026-49245 is fixed in 2.7.3. Upgrade to this version or later.
Whether CVE-2026-49245 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
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.
Upgrade github.com/drakkan/sftpgo/v2 to 2.7.3 or later.