Skip to content

← Actionable
Medium, CVSS 6.4amended

rclone: FTP Command Arguments Permit CRLF Injection When Custom Encoding Preserves Newlines

CVE-2026-71311GHSA-8c48-q9wj-3w37

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/rclone/rclone 1.75.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.4 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:H
EPSS
  • CVE-2026-71311: 0.39% estimated exploitation activity in the next 30 days; percentile 33.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

1. Summary A valid but nondefault FTP filename encoding can restore raw CR/LF immediately before an attacker-controlled path is interpolated into the line-oriented FTP control channel. The dependency does not reject CR or LF in command arguments, so a filename can inject an independent authenticated command. A real test server observed the injected DELE command. The default FTP encoding and the configuration-wizard examples include Ctl and are not vulnerable to the demonstrated filename. A manual custom encoding that omits Ctl/CrLf is mandatory and is reflected as High attack complexity. The credible trust boundary is a lower-trust source namespace feeding a more-privileged FTP destination: if the attacker already has equivalent rights on that destination, the report establishes a bug but no privilege gain. Protocol framing must still be enforced at the command sink because a filename-compatibility encoder is not a safe substitute for command-argument validation. 2. Affected Assets &…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-8c48-q9wj-3w37

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6187

  3. Revision 1 · created ·

    Published from osv record GHSA-8c48-q9wj-3w37

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-71311

Advisory: rclone: FTP Command Arguments Permit CRLF Injection When Custom Encoding Preserves Newlines
IDs: CVE-2026-71311, GHSA-8c48-q9wj-3w37
Record: https://patchnext.com/advisories/cve-2026-71311 (revision 3, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/rclone/rclone 1.75.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/rclone/rclone: affected < 1.75.0; fixed in 1.75.0

## Suggested inspection (read-only)
- Go github.com/rclone/rclone: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/rclone/rclone.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-8c48-q9wj-3w37 (OSV record GHSA-8c48-q9wj-3w37 lists affected ranges: Go github.com/rclone/rclone >=0 <1.75.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6187 (OSV record GO-2026-6187 lists affected ranges: Go github.com/rclone/rclone >=0 <1.75.0 (fixed))
- Verified: https://github.com/advisories/GHSA-8c48-q9wj-3w37 (GitHub-reviewed advisory GHSA-8c48-q9wj-3w37 lists affected ranges: Go github.com/rclone/rclone >=0 <1.75.0)

Commands are suggestions: review each one before running it.

Loading voting…