MediumGHSA-4vr5-p2gc-h23pBIT-rclone-2026-59732CVE-2026-59732GO-2026-6185

rclone archive extract allows S3 destination prefix escape via crafted archive paths

Published 5 Aug 2026 · Updated 10 Sept 2026

Is your project on an affected github.com/rclone/rclone?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<1.74.4
Fixed in
1.74.4
Update to the fixed version for your release line, for example:go get github.com/rclone/rclone@v1.74.4

Details

Summary

rclone archive extract can write extracted files outside the user-selected destination prefix when extracting a crafted archive. A malicious archive entry containing parent path components such as ../ can escape the requested extraction prefix and create or overwrite sibling objects in the same bucket/path scope.

Details

The affected code path is in cmd/archive/extract/extract.go.

In ArchiveExtract(), the archive entry path is taken from f.NameInArchive. The code strips only a leading ./ prefix and then joins the archive entry path with the destination directory:

remote := f.NameInArchive
remote = strings.TrimPrefix(remote, "./")
if dstDir != "" {
    remote = path.Join(dstDir, remote)
}
_, err = operations.Rcat(ctx, dst, remote, fin, f.ModTime(), nil)

Parent path components such as ../ are not rejected before path.Join() is used.

When the destination is an S3-style remote such as:

:s3:bucket/safe/prefix

rclone creates the destination filesystem rooted at bucket/safe and treats prefix as the destination directory. If the archive contains an entry named:

../escaped-from-prefix.txt

then path.Join("prefix", "../escaped-from-prefix.txt") resolves to:

escaped-from-prefix.txt

As a result, the S3 backend uploads the object to:

bucket/safe/escaped-from-prefix.txt

instead of the expected destination:

bucket/safe/prefix/escaped-from-prefix.txt

This allows an attacker-controlled archive to escape the selected extraction prefix on object-storage remotes.

PoC

Test environment:

  • Windows 11
  • rclone v1.74.3 official Windows amd64 binary
  • Local fake S3 HTTP endpoint
  • Crafted ZIP archive containing ../escaped-from-prefix.txt

Steps to reproduce:https://drive.google.com/file/d/1P_cLKFgiWSVSATB8500yP28jdzwt9FAt/view?usp=sharing

1. Extract the attached PoC ZIP.

2. Run the PoC script:

powershell -ExecutionPolicy Bypass -File .\run-poc.ps1 -RcloneExe "C:\path\to\rclone.exe"

3. The PoC creates a ZIP archive containing this entry:

../escaped-from-prefix.txt

4. The PoC starts a local fake S3 endpoint and runs rclone with an S3-style destination prefix:

rclone archive extract malicious.zip :s3:bucket/safe/prefix

5. Observe the fake S3 request log.

Expected safe behavior:

PUT /bucket/safe/prefix/escaped-from-prefix.txt

Observed behavior:

PUT /bucket/safe/escaped-from-prefix.txt?x-id=PutObject

This shows that the archive entry escaped the requested safe/prefix destination and was written under safe/ instead.

The PoC package includes:

  • run-poc.ps1
  • fake-s3-server.py
  • README.md
  • report-draft.md
  • captured proof logs

Impact

An attacker who supplies an archive that a victim extracts with rclone archive extract can cause extracted files to be written outside the destination prefix selected by the victim when the destination is an S3-style object storage remote.

Depending on the victim's configured remote credentials and bucket permissions, this may allow creation or overwrite of sibling objects outside the intended extraction directory/prefix.

This does not require compromising the S3 service itself. The attack relies on the victim extracting an attacker-controlled archive with rclone into an object-storage prefix.

Is GHSA-4vr5-p2gc-h23p in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/rclone/rclone, and gives you the command that fixes it.

More advisories for github.com/rclone/rclone

  • LowCVE-2026-88045rclone: S3 multipart declared-length memory exhaustion in github.com/rclone/rclone · 16 Sept 2026
  • LowCVE-2026-88046rclone: source object names can escape the configured root on upload in github.com/rclone/rclone · 16 Sept 2026
  • LowCVE-2026-88017rclone: FTP cross-session auth-proxy backend confusion in github.com/rclone/rclone · 16 Sept 2026
  • LowCVE-2026-88016rclone: Directory metadata (chmod/chown/chtimes) applied through a planted symlink in rclone local --links escapes the destination in github.com/rclone/rclone · 16 Sept 2026
  • LowCVE-2026-88044rclone: RC per-server auth-proxy bypass in github.com/rclone/rclone · 16 Sept 2026
  • LowCVE-2026-88015rclone local: crafted Range request against a translated symlink panics (DoS) in github.com/rclone/rclone · 16 Sept 2026
All 57 advisories for github.com/rclone/rclone

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.