# CVE-2026-71311: rclone: FTP Command Arguments Permit CRLF Injection When Custom Encoding Preserves Newlines

> Attackers can inject FTP commands via crafted filenames when using non-default encoding, allowing unauthorized file deletion or modification on the destination server.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** BIT-rclone-2026-71311, DEBIAN-CVE-2026-71311, GHSA-8c48-q9wj-3w37, GO-2026-6187, MINI-2q9m-8xxp-v452, MINI-3wv6-8jhj-382v, MINI-434r-wcp8-qxf2, MINI-qg4x-m92j-5rj8, MINI-r39m-w8w4-942x, MINI-rwg9-839r-3mgj, MINI-whm9-28gg-9hcg, MINI-xjh9-2mg7-v4fh, UBUNTU-CVE-2026-71311

## What is CVE-2026-71311?

CVE-2026-71311 is a medium-severity command injection vulnerability in rclone, published on 5 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.75.0, a valid but nondefault FTP filename encoding in backend/ftp/ftp.go can restore raw CR/LF immediately before an attacker-controlled path is interpolated into the line-oriented FTP control channel, and github.com/jlaffaye/ftp formats the argument through textproto.Conn.Cmd without rejecting CR or LF, allowing a filename such as victim CRLF DELE other-secret CRLF NOOP to inject an independent authenticated FTP command when the victim copies or syncs to a more-privileged FTP destination. This issue is fixed in 1.75.0.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

## Which versions are affected by CVE-2026-71311?

4 open source packages ship an affected version, including github.com/rclone/rclone and rclone.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/rclone/rclone` | Go | All versions | 1.75.0 |
| `github.com/rclone/rclone` | Go | All versions | 1.75.0 |
| `github.com/rclone/rclone` | Go | All versions | 1.75.0 |
| `rclone` | Bitnami | All versions | 1.75.0 |

## How do I fix CVE-2026-71311?

Upgrade github.com/rclone/rclone to 1.75.0 or later.

## Is CVE-2026-71311 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-71311 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71311 and fix it if it is affected.

What it is: CVE-2026-71311 is a medium-severity command injection vulnerability in rclone, published on 5 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-71311 exists.

Affected packages and fixed versions:
- github.com/rclone/rclone (Go): affected all versions; fixed in 1.75.0
- github.com/rclone/rclone (Go): affected all versions; fixed in 1.75.0
- github.com/rclone/rclone (Go): affected all versions; fixed in 1.75.0
- rclone (Bitnami): affected all versions; fixed in 1.75.0

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-2026-71311/ (Markdown: https://insights.sbomify.com/CVE-2026-71311/index.md)
```

## Sources

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

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