Skip to content

← Actionable
Medium, CVSS 5.0amended

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

CVE-2026-59732GHSA-4vr5-p2gc-h23p

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/rclone/rclone 1.74.4), 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
5.0 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L
EPSS
  • CVE-2026-59732: 0.26% estimated exploitation activity in the next 30 days; percentile 17.77 (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.

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: Parent path components such as ../ are not rejected before path.Join() is used. When the destination is an S3-style remote such as: rclone creates the destination filesystem rooted at bucket/safe and treats prefix as the destination directory. If the archive contains an entry named: then path.Join("prefix", "../escaped-from-prefix.txt") resolves to: As a result, the S3 backend uploads the object to: instead of the…

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

    Amended from ghsa record GHSA-4vr5-p2gc-h23p

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6185

  3. Revision 1 · created ·

    Published from osv record GHSA-4vr5-p2gc-h23p

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-59732

Advisory: rclone archive extract allows S3 destination prefix escape via crafted archive paths
IDs: CVE-2026-59732, GHSA-4vr5-p2gc-h23p
Record: https://patchnext.com/advisories/cve-2026-59732 (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 5.0)
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.74.4. A vendor fix does not mean a deployment is fixed.

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

## 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-4vr5-p2gc-h23p (OSV record GHSA-4vr5-p2gc-h23p lists affected ranges: Go github.com/rclone/rclone >=0 <1.74.4 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6185 (OSV record GO-2026-6185 lists affected ranges: Go github.com/rclone/rclone >=0 <1.74.4 (fixed))
- Verified: https://github.com/advisories/GHSA-4vr5-p2gc-h23p (GitHub-reviewed advisory GHSA-4vr5-p2gc-h23p lists affected ranges: Go github.com/rclone/rclone >=0 <=1.74.3)

Commands are suggestions: review each one before running it.

Loading voting…