CVE-2026-88044: rclone per-server auth-proxy bypass in FTP and S3

CVE-2026-88044 · Severity: critical · CVSS 9.1 · Published 2026-09-10

rclone is a cloud storage synchronization tool that supports running FTP and S3 protocol servers via remote control (RC) API. When an operator configures an authentication proxy for per-server security, the FTP and S3 server implementations incorrectly ignore this setting and fall back to insecure defaults. For FTP, this allows any client to log in as "anonymous" with an arbitrary password and read, write, or delete files. For S3, clients with valid authentication keys can access the wrong backend filesystem, bypassing the intended per-key routing policy.

Technologies: github.com/rclone/rclone (Go). Vendors: Go.

Quick answers

Is CVE-2026-88044 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-88044 being exploited in the wild.
How severe is CVE-2026-88044?
Critical severity, with a CVSS score of 9.1, published 10 September 2026.
Which products and versions are affected?
github.com/rclone/rclone (Go) >= 1.70.0, < 1.75.1, SEMVER:introduced=1.70.0,fixed=1.75.1.
Is there a fix for CVE-2026-88044?
Yes. github.com/rclone/rclone (Go): upgrade to 1.75.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-88044 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-88044?
Check whether you run github.com/rclone/rclone (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/rclone/rclone (Go): upgrade to 1.75.1 or later
    go get github.com/rclone/rclone@v1.75.1

Technical details

The vulnerability is a configuration scope mismatch in cmd/serve/ftp/ftp.go and cmd/serve/s3/server.go. Both RC adapters parse per-server proxy options (proxyOpt.AuthProxy) from the serve/start request and pass them to their server constructors, but the constructors incorrectly branch on the process-global proxy.Opt.AuthProxy instead of the supplied proxyOpt.AuthProxy. When the global option is empty—the normal case when proxy settings are only configured per RC request—the supplied authentication proxy is silently ignored. For FTP, the code falls back to fixed-backend mode with hardcoded "anonymous" credentials and an empty password that accepts any authentication attempt, exposing file read, write, and delete operations. For S3, the code similarly falls back to the fixed filesystem, allowing holders of any valid auth_key to reach the RC-configured fs instead of the filesystem routed by the auth proxy. The root cause is checking the wrong variable; the fix requires changing the mode-selection logic to test the request-local proxyOpt object. Exploitation requires network access to the FTP or S3 listener and does not require CLI-level changes or global configuration manipulation.

Affected products

  • rclone rclone >=1.70.0, <1.75.1

Identifiers

  • CVE-2026-88044
  • GHSA-p569-5gjg-9cmj
  • GO-2026-6460

Timeline

  • 2026-09-04: disclosed: GitHub Advisory GHSA-p569-5gjg-9cmj published
  • 2026-09-10: advisory: Public advisory with full technical analysis and proof of concept
  • 2026-09-11: patched: Fix released in rclone v1.75.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.