# CVE-2025-24366: Insufficient sanitization of user provided rsync command in SFTPGo

> Authenticated users can inject rsync options to read or write files on the server if the optional rsync command is enabled.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Feb 2025
- **Updated:** 7 Feb 2025
- **Also known as:** GHSA-vj7w-3m8c-6vpx, GO-2025-3458

## What is CVE-2025-24366?

CVE-2025-24366 is a high-severity command injection vulnerability in drakkan sftpgo, published on 7 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SFTPGo is an open source, event-driven file transfer solution. SFTPGo supports execution of a defined set of commands via SSH. Besides a set of default commands some optional commands can be activated, one of them being `rsync`. It is disabled in the default configuration and it is limited to the local filesystem, it does not work with cloud/remote storage backends. Due to missing sanitization of the client provided `rsync` command, an authenticated remote user can use some options of the rsync command to read or write files with the permissions of the SFTPGo server process. This issue was fixed in version v2.6.5 by checking the client provided arguments. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-24366?

6 open source packages ship an affected version, including github.com/drakkan/sftpgo and github.com/drakkan/sftpgo/v2.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/drakkan/sftpgo` | Go | All versions | None |
| `github.com/drakkan/sftpgo` | Go | All versions to 1.2.2 | None |
| `github.com/drakkan/sftpgo` | Go | All versions to 1.2.2 | None |
| `github.com/drakkan/sftpgo/v2` | Go | All versions | 2.6.5 |
| `github.com/drakkan/sftpgo/v2` | Go | From 0.9.5 | 2.6.5 |
| `github.com/drakkan/sftpgo/v2` | Go | From 0.9.5 | 2.6.5 |

## How do I fix CVE-2025-24366?

Upgrade to a fixed version.

## Is CVE-2025-24366 being exploited?

There is no known exploitation of CVE-2025-24366 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24366 and fix it if it is affected.

What it is: CVE-2025-24366 is a high-severity command injection vulnerability in drakkan sftpgo, published on 7 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24366 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/drakkan/sftpgo (Go): affected all versions; no fix listed
- github.com/drakkan/sftpgo (Go): affected all versions up to 1.2.2; no fix listed
- github.com/drakkan/sftpgo (Go): affected all versions up to 1.2.2; no fix listed
- github.com/drakkan/sftpgo/v2 (Go): affected all versions; fixed in 2.6.5
- github.com/drakkan/sftpgo/v2 (Go): affected from 0.9.5; fixed in 2.6.5
- github.com/drakkan/sftpgo/v2 (Go): affected from 0.9.5; fixed in 2.6.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-24366/ (Markdown: https://insights.sbomify.com/CVE-2025-24366/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24366
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24366
- OSV: https://osv.dev/vulnerability/CVE-2025-24366

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-24366/
Summaries are generated and may contain mistakes; the official description above is the record.