CVE-2026-88014: rclone archive/zip Zip Slip Vulnerability

MODERATE
Advisory Identifier: GHSA-66hp-wgxq-6f5q
CVSS 6.3
CWE-22
Published
Advisory Summary

CVE-2026-88014 is a MODERATE (CVSS 6.3) zip slip vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting rclone archive/zip libraries in the Go ecosystem. The issue involves zip slip via unsanitized zip entry names lets a malicious archive escape its own namespace. Remediation is available by upgrading affected packages to version 1.75.1.

CVE-2026-88014 at a Glance

CVE Identifier CVE-2026-88014
GHSA Identifier GHSA-66hp-wgxq-6f5q
Severity MODERATE
CVSS v3.1 Base Score 6.3
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product rclone archive/zip
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-88014

To remediate this vulnerability, upgrade all affected rclone archive/zip dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/rclone/rclone fixed: 1.75.1
Upgrade github.com/rclone/rclone to 1.75.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/rclone/rclone

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-88014, inspect your project dependencies for rclone archive/zip:

inspect dependencies for github.com/rclone/rclone

Analyze the terminal output to locate any version of rclone archive/zip in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.75.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In rclone archive/zip, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary `backend/archive` mounts a zip file as a browsable, syncable rclone `Fs` (e.g. `rclone lsf :zip:downloaded.zip` or `rclone copy :zip:downloaded.zip dest:`). Go's `archive/zip` package does not sanitize `file.Name` - it is taken verbatim from the untrusted zip's central directory. `readZip()` in `backend/archive/zip/zip.go` applies `path.Clean` to the entry name, but this alone cannot fully neutralize a name with more `..` components than real segments preceding them (e.g. `"../../etc/cron.d/evil"` stays exactly as-is after cleaning). When the archive is mounted with an empty root (the common case), there was no check at all that the resulting name stayed inside the archive's own namespace, so it was stored verbatim and returned unchanged by `Object.Remote()`. `fs/sync`/`fs/operations` use `srcObj.Remote()` directly as the destination-relative path when copying between filesystems, so a maliciously crafted zip file can cause `rclone copy`/`sync` to attempt writes outside the intended destination directory on whatever backend it targets - this is the well-known "Zip Slip" vulnerability class (https://security.snyk.io/research/zip-slip-vulnerability) applied to rclone's own zip-mounting backend. It is distinct from `cmd/archive/extract`, which already validates via its own `destPath()` choke point and is not affected. ### Details Vulnerable code (before fix), `backend/archive/zip/zip.go`, `(*Fs).readZip`: ```go for _, file := range zr.File { remote := strings.Trim(path.Clean(file.Name), "/") if remote == "." { remote = "" } remote = path.Join(f.prefix, remote) if f.root != "" { // Ignore all files outside the root if !strings.HasPrefix(remote, f.root) { continue } ... } ... o := &Object{f: f, remote: remote, ...} dt.Add(o) } ``` The escape check only ran when `f.root != ""`, and even then used a bare `strings.HasPrefix` with no boundary check (so `f.root="foo"` incorrectly also matched a sibling entry `"foobar"`). ### PoC Built a zip in memory with Go's real `archive/zip` writer (entry name `"../../etc/cron.d/evil"`, not sanitized by the writer either), wrote it to disk, and mounted it via the actual production constructor `zip.New(ctx, localFs, "evil.zip", "", "")`: ``` zip entry Name="../../etc/cron.d/evil" -> Object.Remote()="../../etc/cron.d/evil" ``` Fully outside the archive's own namespace - confirmed via a regression test that mounts the malicious zip through the real `local` backend and inspects the resulting Fs's internal dirtree and every Object's `Remote()`. ### Impact A user who runs `rclone copy`/`sync`/`mount` against an untrusted zip file (downloaded, e-mailed, etc.) can have files written outside the intended destination directory on the destination backend, depending on that backend's own confinement. No server compromise or custom remote configuration is required from the attacker - only a crafted zip file and a normal `rclone copy`/`sync` invocation by the victim. ### Fix Skip any zip entry whose cleaned+prefixed name still escapes the archive's own namespace, rather than exposing it. Also tightened the pre-existing root filter's weak prefix check.

CVE-2026-88014 Affected rclone archive/zip Versions

1 component(s)
Fixed Versions:
1.75.1
Product / Package Ecosystem Affected Versions Fixed Version
github.com/rclone/rclone
Go
≥ 1.72.0
< 1.75.1
1.75.1

References

Frequently Asked Questions

What is CVE-2026-88014?
CVE-2026-88014 is a security vulnerability in rclone archive/zip involving Zip Slip via unsanitized zip entry names lets a malicious archive escape its own namespace under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which rclone archive/zip versions are affected?
Affected versions include releases prior to 1.75.1 across affected packages: github.com/rclone/rclone.
What version fixes CVE-2026-88014?
Upgrading to 1.75.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/rclone/rclone affected?
Yes, github.com/rclone/rclone is affected in releases prior to 1.75.1. Upgrade your dependency to 1.75.1 or later.
What is the CVSS score of CVE-2026-88014?
CVE-2026-88014 has a CVSS v3.1 base score of 6.3 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N.
What CWE is associated with CVE-2026-88014?
CVE-2026-88014 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check Go dependencies for CVE-2026-88014?
Run the dependency tree command: 'inspect dependencies for github.com/rclone/rclone'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-66hp-wgxq-6f5q",
  "modified" : "2026-09-10T23:03:16Z",
  "published" : "2026-09-10T23:03:16Z",
  "aliases" : [ "CVE-2026-88014" ],
  "summary" : "rclone archive/zip: Zip Slip via unsanitized zip entry names lets a malicious archive escape its own namespace",
  "details" : "### Summary\n`backend/archive` mounts a zip file as a browsable, syncable rclone `Fs` (e.g. `rclone lsf :zip:downloaded.zip` or `rclone copy :zip:downloaded.zip dest:`). Go's `archive/zip` package does not sanitize `file.Name` - it is taken verbatim from the untrusted zip's central directory. `readZip()` in `backend/archive/zip/zip.go` applies `path.Clean` to the entry name, but this alone cannot fully neutralize a name with more `..` components than real segments preceding them (e.g. `\"../../etc/cron.d/evil\"` stays exactly as-is after cleaning). When the archive is mounted with an empty root (the common case), there was no check at all that the resulting name stayed inside the archive's own namespace, so it was stored verbatim and returned unchanged by `Object.Remote()`.\n\n`fs/sync`/`fs/operations` use `srcObj.Remote()` directly as the destination-relative path when copying between filesystems, so a maliciously crafted zip file can cause `rclone copy`/`sync` to attempt writes outside the intended destination directory on whatever backend it targets - this is the well-known \"Zip Slip\" vulnerability class (https://security.snyk.io/research/zip-slip-vulnerability) applied to rclone's own zip-mounting backend. It is distinct from `cmd/archive/extract`, which already validates via its own `destPath()` choke point and is not affected.\n\n### Details\nVulnerable code (before fix), `backend/archive/zip/zip.go`, `(*Fs).readZip`:\n```go\nfor _, file := range zr.File {\n\tremote := strings.Trim(path.Clean(file.Name), \"/\")\n\tif remote == \".\" { remote = \"\" }\n\tremote = path.Join(f.prefix, remote)\n\tif f.root != \"\" {\n\t\t// Ignore all files outside the root\n\t\tif !strings.HasPrefix(remote, f.root) { continue }\n\t\t...\n\t}\n\t...\n\to := &Object{f: f, remote: remote, ...}\n\tdt.Add(o)\n}\n```\nThe escape check only ran when `f.root != \"\"`, and even then used a bare `strings.HasPrefix` with no boundary check (so `f.root=\"foo\"` incorrectly also matched a sibling entry `\"foobar\"`).\n\n### PoC\nBuilt a zip in memory with Go's real `archive/zip` writer (entry name `\"../../etc/cron.d/evil\"`, not sanitized by the writer either), wrote it to disk, and mounted it via the actual production constructor `zip.New(ctx, localFs, \"evil.zip\", \"\", \"\")`:\n```\nzip entry Name=\"../../etc/cron.d/evil\" -> Object.Remote()=\"../../etc/cron.d/evil\"\n```\nFully outside the archive's own namespace - confirmed via a regression test that mounts the malicious zip through the real `local` backend and inspects the resulting Fs's internal dirtree and every Object's `Remote()`.\n\n### Impact\nA user who runs `rclone copy`/`sync`/`mount` against an untrusted zip file (downloaded, e-mailed, etc.) can have files written outside the intended destination directory on the destination backend, depending on that backend's own confinement. No server compromise or custom remote configuration is required from the attacker - only a crafted zip file and a normal `rclone copy`/`sync` invocation by the victim.\n\n### Fix\nSkip any zip entry whose cleaned+prefixed name still escapes the archive's own namespace, rather than exposing it. Also tightened the pre-existing root filter's weak prefix check.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rclone/rclone"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.72.0"
      }, {
        "fixed" : "1.75.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/rclone/rclone/security/advisories/GHSA-66hp-wgxq-6f5q"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-88014"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rclone/rclone/commit/5dae3adbf571a6cd9ba501eb47397a7e871e1ae0"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rclone/rclone/commit/6507e13d5a83789f500af96d7188c302c9d74d98"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/rclone/rclone"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rclone/rclone/releases/tag/v1.75.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-10T23:03:16Z",
    "nvd_published_at" : "2026-09-10T16:18:08Z"
  }
}