Is CVE-2026-88046 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-88046 being exploited in the wild.

How severe is CVE-2026-88046?

Medium severity, with a CVSS score of 5.3, published 10 September 2026.

Which products and versions are affected?

github.com/rclone/rclone (Go) < 1.75.1, SEMVER:introduced=0,fixed=1.75.1.

Is there a fix for CVE-2026-88046?

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-88046 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-88046?

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.

CVE-2026-88046: rclone path traversal via object name escaping on upload

Q: Is there a fix for CVE-2026-88046?

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.

Q: How is CVE-2026-88046 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-88046?

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.

CVE-2026-88046 · Severity: medium · CVSS 5.3 · Published 2026-09-10

rclone is a command-line tool used to synchronize files between local storage and cloud/remote backends (like AWS S3, Azure, SFTP, etc.). The tool fails to properly validate source object names when copying data, allowing specially crafted filenames containing ".." path segments to escape the configured destination directory and land in unintended locations within the operator's own account. An attacker who can inject objects into a source store that rclone reads from can redirect data to different buckets, shares, or paths the operator has access to, compromising data integrity and enabling misplacement of sensitive backups or configurations.

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

Quick answers

Is CVE-2026-88046 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-88046 being exploited in the wild.
How severe is CVE-2026-88046?: Medium severity, with a CVSS score of 5.3, published 10 September 2026.
Which products and versions are affected?: github.com/rclone/rclone (Go) < 1.75.1, SEMVER:introduced=0,fixed=1.75.1.
Is there a fix for CVE-2026-88046?: 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-88046 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-88046?: 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

This is a path traversal vulnerability (CWE-22) in rclone's core synchronization logic. The rclone core does not sanitize ".." segments in object names before passing them to backend drivers. When backends (B2, Swift, SFTP, SMB, FTP, WebDAV, and others) construct destination paths via path.Join(root, remote), these ".." segments are resolved before encoding is applied, allowing traversal outside the configured root directory. The vulnerability requires two preconditions: (1) the source must be a flat-keyspace object store (S3, B2, Swift, etc., not a filesystem), and (2) the malicious object must have been created with native tooling (not rclone itself, which encodes ".." to fullwidth "．．"). An attacker using native AWS S3 API calls can upload an object with key "../../victim-backups/pwned.txt"; when a victim runs rclone copy to ingest from that source, the file lands in the wrong location within their own account. For SFTP and SMB backends, the blast radius extends to the filesystem or other shares accessible by the login credential. Fixed in rclone v1.75.1.

Affected products

rclone rclone < 1.75.1

Identifiers

CVE-2026-88046
GHSA-38xv-hf3p-h7mq
GO-2026-6457

Timeline

2026-09-10: disclosed: Public advisory published via GitHub and NVD
2026-09-10: patched: Fix available in rclone v1.75.1

References

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