CVE-2026-59732
rclone archive extract allows S3 destination prefix escape via crafted archive paths
Rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.74.4, rclone archive extract can write extracted files outside the user-selected destination prefix when extracting a crafted archive containing parent path components such as ../, allowing creation or overwrite of sibling objects in the same bucket or path scope. This issue is fixed in version 1.74.4.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
What an attacker can affect
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
Exploit likelihood
What each source reports
CVE List Score used
5.0
rclone archive extract allows S3 destination prefix escape via crafted archive paths
Rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.74.4, rclone archive extract can write extracted files outside the user-selected destination prefix when extracting a crafted archive containing parent path components such as ../, allowing creation or overwrite of sibling objects in the same bucket or path scope. This issue is fixed in version 1.74.4.
- Record
CVE-2026-59732- CVSS 3.1
- 5.0 Medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L - Weakness
- CWE-22
- Updated
- 2026-11-02
EUVDEUVD-2026-44530
5.0
Rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.74.4, rclone archive extract can write extracted files outside the user-selected destination prefix when extracting a crafted archive containing parent path components such as ../, allowing creation or overwrite of sibling objects in the same bucket or path scope. This issue is fixed in version 1.74.4.
- Record
EUVD-2026-44530- CVSS 3.1
- 5.0 Medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-4vr5-p2gc-h23p
5.0
rclone archive extract allows S3 destination prefix escape via crafted archive paths
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
-
Extract the attached PoC ZIP.
-
Run the PoC script:
powershell -ExecutionPolicy Bypass -File .\run-poc.ps1 -RcloneExe "C:\path\to\rclone.exe"
- The PoC creates a ZIP archive containing this entry:
../escaped-from-prefix.txt
- 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
- 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.ps1fake-s3-server.pyREADME.mdreport-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.
- Record
GHSA-4vr5-p2gc-h23p- CVSS 3.1
- 5.0 Medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L - Weakness
- CWE-22
- Updated
- 2026-11-02
NVD
5.0
Rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.74.4, rclone archive extract can write extracted files outside the user-selected destination prefix when extracting a crafted archive containing parent path components such as ../, allowing creation or overwrite of sibling objects in the same bucket or path scope. This issue is fixed in version 1.74.4.
- Record
CVE-2026-59732- CVSS 3.1
- 5.0 Medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L - Weakness
- CWE-22
- Updated
- 2026-11-02
OSV
5.0
rclone archive extract allows S3 destination prefix escape via crafted archive paths
Rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.74.4, rclone archive extract can write extracted files outside the user-selected destination prefix when extracting a crafted archive containing parent path components such as ../, allowing creation or overwrite of sibling objects in the same bucket or path scope. This issue is fixed in version 1.74.4.
- Record
CVE-2026-59732- CVSS 3.1
- 5.0 Medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L - Weakness
- CWE-22
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2026-59732
5.0
Rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.74.4, rclone archive extract can write extracted files outside the user-selected destination prefix when extracting a crafted archive containing parent path components such as ../, allowing creation or overwrite of sibling objects in the same bucket or path scope. This issue is fixed in version 1.74.4.
- Record
DEBIAN-CVE-2026-59732- CVSS 3.1
- 5.0 Medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L - Updated
- 2026-11-02
Show 8 moreShow less
OSVGHSA-4vr5-p2gc-h23p
5.0
rclone archive extract allows S3 destination prefix escape via crafted archive paths
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
-
Extract the attached PoC ZIP.
-
Run the PoC script:
powershell -ExecutionPolicy Bypass -File .\run-poc.ps1 -RcloneExe "C:\path\to\rclone.exe"
- The PoC creates a ZIP archive containing this entry:
../escaped-from-prefix.txt
- 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
- 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.ps1fake-s3-server.pyREADME.mdreport-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.
- Record
GHSA-4vr5-p2gc-h23p- CVSS 3.1
- 5.0 Medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L - Weakness
- CWE-22
- Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-59732
5.0
Rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.74.4, rclone archive extract can write extracted files outside the user-selected destination prefix when extracting a crafted archive containing parent path components such as ../, allowing creation or overwrite of sibling objects in the same bucket or path scope. This issue is fixed in version 1.74.4.
- Record
UBUNTU-CVE-2026-59732- CVSS 3.1
- 5.0 Medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L - Updated
- 2026-11-02
OSVBIT-rclone-2026-59732 No score
rclone archive extract allows S3 destination prefix escape via crafted archive paths
Rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.74.4, rclone archive extract can write extracted files outside the user-selected destination prefix when extracting a crafted archive containing parent path components such as ../, allowing creation or overwrite of sibling objects in the same bucket or path scope. This issue is fixed in version 1.74.4.
- Record
BIT-rclone-2026-59732- Updated
- 2026-11-02
OSVGO-2026-6185 No score
Path traversal via crafted archive paths in github.com/rclone/rclone
Path traversal via crafted archive paths in github.com/rclone/rclone
- Record
GO-2026-6185- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:11241-1 No score
rclone-1.74.4-1.1 on GA media
These are all security issues fixed in the rclone-1.74.4-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:11241-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21436-1 No score
Security update for rclone
This update for rclone fixes the following issues:
Changes in rclone:
-
Update to version 1.74.4 (boo#1267192):
- Version v1.74.4
- gui: update embedded release to 1.1.10
- local: stop --links symlinks escaping the destination directory CVE-2026-54572
- local: don't restore setuid/setgid/sticky bits from metadata by default GHSA-945v-v9p3-v5xw
- s3: strip STS security token on same-host HTTPS->HTTP redirect GHSA-cf44-9pgv-m4xc
- serve restic: fix --private-repos isolation bypass CVE-2026-59733
- archive extract: fix path traversal letting archives escape the destination CVE-2026-59732
- serve s3: fix path traversal letting clients see files in the root GHSA-8v25-v8p6-qf7v
- build: fix multiple CVEs by upgrading to go1.26.5
- s3: fix mounting a prefix failing with 403 when HEAD is not permitted
- drive, googlephotos: warn when using rclone's shared client_id #9580
- drive: fix stray %!(EXTRA) in unexportable google document log message
- serve/http: fix --disable-zip so it works over rc
- serve webdav: fix MOVE overwrite failing without Overwrite header
- fs: fix negative offset when a suffix Range request exceeds object size
- accounting: fix goroutine leak in NewStatsGroup for zero-transfer rc jobs
- cmd/mount2: fix NFS directory listings by supporting non-zero Seekdir offsets
- cmd/mount2: fix ESTALE over NFS by reporting stable inode numbers
- cmd/mount2: fix NFS file creation by implementing Mknod
- smb: fix for IBM iSeries and signature verification
- mega: fix hard deleted files reappearing in listings - fixes #9554
- mega: wait for server events after upload, delete and move
- vfs: fix hang reopening a file during the handle-caching grace period
- s3: correct documented copy_cutoff minimum to 1 byte - Fixes #7391
- fs: fix command line flag being ignored when set to its default value
- docs: fix copy to clipboard functionality for code blocks
- fs/operations: correct DeleteFile --backup-dir documentation
- build: update golang.org/x/image to v0.43.0 to fix image decoding vulnerabilities
- docs: clarify copyto command description - Fixes #9527
- docs: fix typo in remote setup docs
- serve s3: fix spurious 404 on HEAD/GET during VFS writeback - fixes #8188
-
- s3: fix error mapping in GetObject to match HeadObject
- filter: fix --files-from copy stopping at the first unreadable file
- docs: Fix RELEASE.md
- ncdu: fix duplicated keystrokes on Windows by pinning tcell to v2.9.0
- completion: fix powershell completion corrupting non-ASCII names - fixes #9412
- docs/crypt: fix encrypted size example - Fixes #9202
- docs: drive: note Google verification exemption for personal use apps
- rc: document that rc API access is equivalent to shell access
- docs: drive: update documentation about "Computers" folder
- accounting: fix goroutine leak in ResetCounters
- docs: fix --windows-event-log-level help
- backend/filelu: fix recursive listing path handling and file filtering
- docs: bisync - clarify flag interaction and minor changes
- docs: Update RELEASE.md to use cherry-pick -x
- webdav: fix mixed property statuses in multi-status responses
- s3: remove session token on cross-host redirects
- drive: warn when non-exportable Google documents are skipped - #9475
- Start v1.74.4-DEV development
-
update x/image to 0.43 (bsc#1271056)
-
Update to version 1.74.3: (boo#1267869)
- Bug Fixes
- rc
- Fix unauthenticated command execution via --rc-serve inline remotes CVE-2026-49980 (Nick Craig-Wood)
- Stop global.* connection string options changing config CVE-2026-49980 (Nick Craig-Wood)
- build: Fix multiple CVEs by upgrading to go1.26.4 (Nick
Craig-Wood)
- CVE-2026-42504: mime: quadratic complexity in WordDecoder.DecodeHeader
- CVE-2026-42507: net/textproto: arbitrary input are included in errors without any escaping
- CVE-2026-27145: crypto/x509: split…
- rc
- Bug Fixes
- Record
openSUSE-SU-2026:21436-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21761-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
-
Update to version 0.0.20260827T195228 2026-08-27T19:52:28Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-5026 CVE-2026-39821
- GO-2026-6225
- GO-2026-6250 CVE-2026-63328 GHSA-8rc5-4fr6-64pw
- GO-2026-6253 CVE-2026-17106 GHSA-hfg8-hc9c-6c3h
- GO-2026-6254 CVE-2026-53941 GHSA-vjhx-2cqw-3q6q
- GO-2026-6255 CVE-2026-61711 GHSA-7236-3392-c5c6
- GO-2026-6256 CVE-2026-61712 GHSA-72x6-4j93-7w86
- GO-2026-6258 CVE-2026-45404 GHSA-42cj-99w8-cp2p
- GO-2026-6259 CVE-2026-32637 GHSA-j2g6-362q-6qc6
- GO-2026-6260 CVE-2026-55149 GHSA-qqff-5854-px68
- GO-2026-6261 CVE-2026-54061 GHSA-rrwh-6jrq-wp5v
- GO-2026-6262 GHSA-22w5-2fxg-vrwx
- GO-2026-6263 CVE-2026-54168 GHSA-6f2p-296r-cc28
- GO-2026-6264 CVE-2026-54245 GHSA-7q96-f8xw-jv5j
- GO-2026-6265 GHSA-8fxq-53rx-ph5f
- GO-2026-6266 CVE-2026-54167 GHSA-f5f4-3hh4-f54m
- GO-2026-6267 GHSA-h58c-xccx-75m3
- GO-2026-6268 GHSA-q9c5-pp7m-fm2g
- GO-2026-6269 GHSA-rxhg-vcww-2mpw
- GO-2026-6270 CVE-2026-54162 GHSA-x3g7-qrwc-f6c5
- GO-2026-6271 CVE-2026-67448 GHSA-8r62-w5wh-fc5m
- GO-2026-6272 CVE-2026-67447 GHSA-r553-m4fv-5v97
- GO-2026-6273 CVE-2026-64679 GHSA-26w5-6g95-gj28
- GO-2026-6274 CVE-2026-76905 GHSA-mmfr-pmjx-hw9w
- GO-2026-6275 CVE-2026-77354 GHSA-xhj3-7xw9-vr34
- GO-2026-6277 GHSA-4ph6-mjv7-3fq6
- GO-2026-6278 GHSA-w67g-5rqw-f597
- GO-2026-6279 CVE-2026-6046 GHSA-3vmp-whvv-5v9v
- GO-2026-6280 CVE-2026-7387 GHSA-6hxm-w4hv-vgvw
- GO-2026-6281 CVE-2026-6961 GHSA-8qq9-cqj8-82w4
- GO-2026-6282 CVE-2026-7184 GHSA-9p44-r552-4wp9
- GO-2026-6283 CVE-2026-6689 GHSA-c28q-m4gf-vg4q
- GO-2026-6284 CVE-2026-55477 GHSA-jm48-m3rr-9hgg
- GO-2026-6285 CVE-2026-6739 GHSA-m2w9-h2mm-79qr
- GO-2026-6286 CVE-2026-3433 GHSA-rp4v-qc77-phm4
- GO-2026-6287 GHSA-vx2m-jpxr-xv7w
- GO-2026-6288 CVE-2026-11624 GHSA-76g7-m3xw-x9gr
- GO-2026-6289 GHSA-w8j7-39hp-8x59
- GO-2026-6290 CVE-2026-55581 GHSA-3x77-wg38-92r3
- GO-2026-6291 CVE-2026-55582 GHSA-74hp-mggr-hv58
- GO-2026-6292 CVE-2026-55580 GHSA-f5pj-2738-996m
- GO-2026-6293 CVE-2026-55677 GHSA-vfp3-v2gw-7wfq
- GO-2026-6294 CVE-2026-55092 GHSA-mcj4-mphf-j9ff
- GO-2026-6295 CVE-2026-55637 GHSA-cmwv-wf9p-p8wx
- GO-2026-6296 CVE-2026-54523 GHSA-79gf-7frw-68m9
- GO-2026-6297 CVE-2026-50879 GHSA-g743-m6x3-v6wm
- GO-2026-6298 CVE-2026-54563 GHSA-w5fv-7x5q-g8qp
- GO-2026-6299 CVE-2026-50884 GHSA-5442-mh7f-72px
- GO-2026-6300 CVE-2026-50891 GHSA-rcqf-cpv9-g5jf
- GO-2026-6301 CVE-2026-42350 GHSA-g7gw-m874-7rmf
-
Update to version 0.0.20260819T170606 2026-08-19T17:06:06Z.
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4720 GHSA-v3mg-9v85-fcm7
- GO-2026-4942 CVE-2026-35172 GHSA-f2g3-hh2r-cwgc
- GO-2026-4950
- GO-2026-6093 GHSA-464c-974j-9xm6
- GO-2026-6094 GHSA-gcjh-h69q-9w9g
- GO-2026-6095 GHSA-r277-6w6q-xmqw
- GO-2026-6097 CVE-2026-55495 GHSA-49h3-cwhj-4737
- GO-2026-6098 CVE-2026-55496 GHSA-8r7f-r8hj-r3rv
- GO-2026-6099 CVE-2026-57497 GHSA-g35j-m5xg-vh3q
- GO-2026-6100 CVE-2026-55497 GHSA-g9j2-8w95-3vwv
- GO-2026-6101 CVE-2026-55502 GHSA-hq88-5x99-x3gf
- GO-2026-6102 CVE-2026-55499 GHSA-w8x7-h2px-xmq8
- GO-2026-6103 CVE-2026-73564 GHSA-26gq-p25f-99cp
- GO-2026-6104 CVE-2026-62323 GHSA-c3jm-gv5r-9wcp
- GO-2026-6105 GHSA-c534-2w9c-x7fm
- GO-2026-6106 GHSA-v6w6-358x-2433
- GO-2026-6107 CVE-2026-73500 GHSA-6vch-q96h-7gc3
- GO-2026-6108 CVE-2026-73505 GHSA-6xj8-qv9j-xcjq
- GO-2026-6109 GHSA-86cx-wwf4-phq4
- GO-2026-6110 CVE-2026-73509 GHSA-95cv-r8x4-vh75
- GO-2026-6111 CVE-2026-73506 GHSA-fwjx-9p69-h25h
- GO-2026-6112 CVE-2026-73502 GHSA-jpcw-4wr7-c3vq
- GO-2026-6113 GHSA-p6ph-3jx2-3337
- GO-2026-6114 CVE-2026-73499 GHSA-xg4h-6gfc-h4m8
- GO-2026-6115 CVE-2026-56867
- GO-2026-6117 GHSA-hp74-gm6m-2qm5
- GO-2026-6118 CVE-2026-47427 GHSA-w4q6-qw23-4rg7
- GO-2026-6119 CVE-2026-43983…
- Record
openSUSE-SU-2026:21761-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:23625-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
-
Update to version 0.0.20260827T195228 2026-08-27T19:52:28Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-5026 CVE-2026-39821
- GO-2026-6225
- GO-2026-6250 CVE-2026-63328 GHSA-8rc5-4fr6-64pw
- GO-2026-6253 CVE-2026-17106 GHSA-hfg8-hc9c-6c3h
- GO-2026-6254 CVE-2026-53941 GHSA-vjhx-2cqw-3q6q
- GO-2026-6255 CVE-2026-61711 GHSA-7236-3392-c5c6
- GO-2026-6256 CVE-2026-61712 GHSA-72x6-4j93-7w86
- GO-2026-6258 CVE-2026-45404 GHSA-42cj-99w8-cp2p
- GO-2026-6259 CVE-2026-32637 GHSA-j2g6-362q-6qc6
- GO-2026-6260 CVE-2026-55149 GHSA-qqff-5854-px68
- GO-2026-6261 CVE-2026-54061 GHSA-rrwh-6jrq-wp5v
- GO-2026-6262 GHSA-22w5-2fxg-vrwx
- GO-2026-6263 CVE-2026-54168 GHSA-6f2p-296r-cc28
- GO-2026-6264 CVE-2026-54245 GHSA-7q96-f8xw-jv5j
- GO-2026-6265 GHSA-8fxq-53rx-ph5f
- GO-2026-6266 CVE-2026-54167 GHSA-f5f4-3hh4-f54m
- GO-2026-6267 GHSA-h58c-xccx-75m3
- GO-2026-6268 GHSA-q9c5-pp7m-fm2g
- GO-2026-6269 GHSA-rxhg-vcww-2mpw
- GO-2026-6270 CVE-2026-54162 GHSA-x3g7-qrwc-f6c5
- GO-2026-6271 CVE-2026-67448 GHSA-8r62-w5wh-fc5m
- GO-2026-6272 CVE-2026-67447 GHSA-r553-m4fv-5v97
- GO-2026-6273 CVE-2026-64679 GHSA-26w5-6g95-gj28
- GO-2026-6274 CVE-2026-76905 GHSA-mmfr-pmjx-hw9w
- GO-2026-6275 CVE-2026-77354 GHSA-xhj3-7xw9-vr34
- GO-2026-6277 GHSA-4ph6-mjv7-3fq6
- GO-2026-6278 GHSA-w67g-5rqw-f597
- GO-2026-6279 CVE-2026-6046 GHSA-3vmp-whvv-5v9v
- GO-2026-6280 CVE-2026-7387 GHSA-6hxm-w4hv-vgvw
- GO-2026-6281 CVE-2026-6961 GHSA-8qq9-cqj8-82w4
- GO-2026-6282 CVE-2026-7184 GHSA-9p44-r552-4wp9
- GO-2026-6283 CVE-2026-6689 GHSA-c28q-m4gf-vg4q
- GO-2026-6284 CVE-2026-55477 GHSA-jm48-m3rr-9hgg
- GO-2026-6285 CVE-2026-6739 GHSA-m2w9-h2mm-79qr
- GO-2026-6286 CVE-2026-3433 GHSA-rp4v-qc77-phm4
- GO-2026-6287 GHSA-vx2m-jpxr-xv7w
- GO-2026-6288 CVE-2026-11624 GHSA-76g7-m3xw-x9gr
- GO-2026-6289 GHSA-w8j7-39hp-8x59
- GO-2026-6290 CVE-2026-55581 GHSA-3x77-wg38-92r3
- GO-2026-6291 CVE-2026-55582 GHSA-74hp-mggr-hv58
- GO-2026-6292 CVE-2026-55580 GHSA-f5pj-2738-996m
- GO-2026-6293 CVE-2026-55677 GHSA-vfp3-v2gw-7wfq
- GO-2026-6294 CVE-2026-55092 GHSA-mcj4-mphf-j9ff
- GO-2026-6295 CVE-2026-55637 GHSA-cmwv-wf9p-p8wx
- GO-2026-6296 CVE-2026-54523 GHSA-79gf-7frw-68m9
- GO-2026-6297 CVE-2026-50879 GHSA-g743-m6x3-v6wm
- GO-2026-6298 CVE-2026-54563 GHSA-w5fv-7x5q-g8qp
- GO-2026-6299 CVE-2026-50884 GHSA-5442-mh7f-72px
- GO-2026-6300 CVE-2026-50891 GHSA-rcqf-cpv9-g5jf
- GO-2026-6301 CVE-2026-42350 GHSA-g7gw-m874-7rmf
-
Update to version 0.0.20260819T170606 2026-08-19T17:06:06Z.
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4720 GHSA-v3mg-9v85-fcm7
- GO-2026-4942 CVE-2026-35172 GHSA-f2g3-hh2r-cwgc
- GO-2026-4950
- GO-2026-6093 GHSA-464c-974j-9xm6
- GO-2026-6094 GHSA-gcjh-h69q-9w9g
- GO-2026-6095 GHSA-r277-6w6q-xmqw
- GO-2026-6097 CVE-2026-55495 GHSA-49h3-cwhj-4737
- GO-2026-6098 CVE-2026-55496 GHSA-8r7f-r8hj-r3rv
- GO-2026-6099 CVE-2026-57497 GHSA-g35j-m5xg-vh3q
- GO-2026-6100 CVE-2026-55497 GHSA-g9j2-8w95-3vwv
- GO-2026-6101 CVE-2026-55502 GHSA-hq88-5x99-x3gf
- GO-2026-6102 CVE-2026-55499 GHSA-w8x7-h2px-xmq8
- GO-2026-6103 CVE-2026-73564 GHSA-26gq-p25f-99cp
- GO-2026-6104 CVE-2026-62323 GHSA-c3jm-gv5r-9wcp
- GO-2026-6105 GHSA-c534-2w9c-x7fm
- GO-2026-6106 GHSA-v6w6-358x-2433
- GO-2026-6107 CVE-2026-73500 GHSA-6vch-q96h-7gc3
- GO-2026-6108 CVE-2026-73505 GHSA-6xj8-qv9j-xcjq
- GO-2026-6109 GHSA-86cx-wwf4-phq4
- GO-2026-6110 CVE-2026-73509 GHSA-95cv-r8x4-vh75
- GO-2026-6111 CVE-2026-73506 GHSA-fwjx-9p69-h25h
- GO-2026-6112 CVE-2026-73502 GHSA-jpcw-4wr7-c3vq
- GO-2026-6113 GHSA-p6ph-3jx2-3337
- GO-2026-6114 CVE-2026-73499 GHSA-xg4h-6gfc-h4m8
- GO-2026-6115 CVE-2026-56867
- GO-2026-6117 GHSA-hp74-gm6m-2qm5
- GO-2026-6118 CVE-2026-47427 GHSA-w4q6-qw23-4rg7
- GO-2026-6119 CVE-2026-43983…
- Record
SUSE-SU-2026:23625-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/rclone/rcloneGo |
through 1.74.3 | 1.74.4 |
rcloneBitnami |
before 1.74.4 | 1.74.4 |
rcloneDebian:12 |
All versions, plus listed versions 1.60.1+dfsg-21.60.1+dfsg-31.60.1+dfsg-41.65.0+dfsg-11.65.0+dfsg-21.69.3+dfsg-11.69.3+dfsg-21.69.3+dfsg-3 |
None known |
rcloneDebian:13 |
All versions, plus listed versions 1.60.1+dfsg-41.65.0+dfsg-11.65.0+dfsg-21.69.3+dfsg-11.69.3+dfsg-21.69.3+dfsg-3 |
None known |
github.com/rclone/rcloneGo |
before 1.74.4 | 1.74.4 |
govulncheck-vulndbSUSE:Linux Enterprise Server 16.0 From an advisory covering 181 CVEs |
before 0.0.20260827T195228-160000.1.1 | 0.0.20260827T195228-160000.1.1 |
govulncheck-vulndbSUSE:Linux Enterprise Server for SAP applications 16.0 From an advisory covering 181 CVEs |
before 0.0.20260827T195228-160000.1.1 | 0.0.20260827T195228-160000.1.1 |
rcloneUbuntu:18.04:LTS |
All versions, plus listed versions 1.36-31.36-3ubuntu0.11.36-3ubuntu0.2 |
None known |
rcloneUbuntu:Pro:20.04:LTS |
All versions, plus listed versions 1.47.0+ex1-61.47.0+ex1-71.49.5-21.49.5-31.50.2-21.50.2-2ubuntu0.11.50.2-2ubuntu0.21.50.2-2ubuntu0.2+esm1 |
None known |
rcloneUbuntu:Pro:22.04:LTS |
All versions, plus listed versions 1.53.3-11.53.3-21.53.3-41.53.3-4ubuntu11.53.3-4ubuntu1.22.04.1 Show 7 moreShow less1.53.3-4ubuntu1.22.04.21.53.3-4ubuntu1.22.04.31.53.3-4ubuntu1.22.04.3+esm11.53.3-4ubuntu1.22.04.41.53.3-4ubuntu1.22.04.4+esm11.53.3-4ubuntu1.22.04.51.53.3-4ubuntu1.22.04.5+esm1 |
None known |
Show 6 moreShow less
| Package | Affected | Fixed |
|---|---|---|
rcloneUbuntu:Pro:24.04:LTS |
All versions, plus listed versions 1.60.1+dfsg-2build11.60.1+dfsg-31.60.1+dfsg-3ubuntu0.24.04.11.60.1+dfsg-3ubuntu0.24.04.21.60.1+dfsg-3ubuntu0.24.04.3 Show 6 moreShow less1.60.1+dfsg-3ubuntu0.24.04.41.60.1+dfsg-3ubuntu0.24.04.4+esm11.60.1+dfsg-3ubuntu0.24.04.51.60.1+dfsg-3ubuntu0.24.04.5+esm11.60.1+dfsg-3ubuntu0.24.04.61.60.1+dfsg-3ubuntu0.24.04.6+esm1 |
None known |
rcloneUbuntu:26.10 |
All versions, plus listed versions 1.60.1+dfsg-4ubuntu31.69.3+dfsg-31.69.3+dfsg-3ubuntu1 |
None known |
rcloneUbuntu:Pro:26.04:LTS |
All versions, plus listed versions 1.60.1+dfsg-4ubuntu21.60.1+dfsg-4ubuntu31.60.1+dfsg-4ubuntu3.11.60.1+dfsg-4ubuntu3.1+esm11.60.1+dfsg-4ubuntu3.21.60.1+dfsg-4ubuntu3.2+esm1 |
None known |
rcloneopenSUSE:Tumbleweed From an advisory covering 3 CVEs |
before 1.74.4-1.1 | 1.74.4-1.1 |
rcloneopenSUSE:Leap 16.0 From an advisory covering 37 CVEs |
before 1.74.4-bp160.1.1 | 1.74.4-bp160.1.1 |
govulncheck-vulndbopenSUSE:Leap 16.0 From an advisory covering 181 CVEs |
before 0.0.20260827T195228-160000.1.1 | 0.0.20260827T195228-160000.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-59732 is a medium vulnerability (CVSS 5.0) in Rclone, published July 9, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.26%, the 17th percentile. Fixed in github.com/rclone/rclone 1.74.4.
References
github.com/rclone/rclone/security/advisories/GHSA-4vr5-p2gc-h23p
github.com/rclone/rclone/commit/1a746732441e8158f32fab35924b23701e719a8c
github.com/rclone/rclone/commit/d11efe0d58fe6a2d6d90675bb9d8ee5840c51e1d
github.com/rclone/rclone/releases/tag/v1.74.4
nvd.nist.gov/vuln/detail/CVE-2026-59732
github.com/advisories/GHSA-4vr5-p2gc-h23p
Show 194 moreShow less
github.com/CVEProject/cvelistV5/tree/main/cves/2026/59xxx/CVE-2026-59732.json
security-tracker.debian.org/tracker/CVE-2026-59732
github.com/rclone/rclone
suse.com/support/update/announcement/2026/suse-su-202623625-1
suse.com/security/cve/CVE-2026-10722
suse.com/security/cve/CVE-2026-11465
suse.com/security/cve/CVE-2026-11479
suse.com/security/cve/CVE-2026-11481
suse.com/security/cve/CVE-2026-11500
suse.com/security/cve/CVE-2026-11624
suse.com/security/cve/CVE-2026-17106
suse.com/security/cve/CVE-2026-25688
suse.com/security/cve/CVE-2026-25699
suse.com/security/cve/CVE-2026-25700
suse.com/security/cve/CVE-2026-32637
suse.com/security/cve/CVE-2026-33582
suse.com/security/cve/CVE-2026-33818
suse.com/security/cve/CVE-2026-34031
suse.com/security/cve/CVE-2026-34033
suse.com/security/cve/CVE-2026-34177
suse.com/security/cve/CVE-2026-34178
suse.com/security/cve/CVE-2026-34179
suse.com/security/cve/CVE-2026-3433
suse.com/security/cve/CVE-2026-34905
suse.com/security/cve/CVE-2026-34976
suse.com/security/cve/CVE-2026-35172
suse.com/security/cve/CVE-2026-35511
suse.com/security/cve/CVE-2026-39821
suse.com/security/cve/CVE-2026-39832
suse.com/security/cve/CVE-2026-39833
suse.com/security/cve/CVE-2026-39904
suse.com/security/cve/CVE-2026-40173
suse.com/security/cve/CVE-2026-41179
suse.com/security/cve/CVE-2026-41181
suse.com/security/cve/CVE-2026-41327
suse.com/security/cve/CVE-2026-41568
suse.com/security/cve/CVE-2026-42350
suse.com/security/cve/CVE-2026-42508
suse.com/security/cve/CVE-2026-43983
suse.com/security/cve/CVE-2026-45099
suse.com/security/cve/CVE-2026-45404
suse.com/security/cve/CVE-2026-46600
suse.com/security/cve/CVE-2026-46603
suse.com/security/cve/CVE-2026-47427
suse.com/security/cve/CVE-2026-48119
suse.com/security/cve/CVE-2026-48491
suse.com/security/cve/CVE-2026-48786
suse.com/security/cve/CVE-2026-49446
suse.com/security/cve/CVE-2026-49447
suse.com/security/cve/CVE-2026-49980
suse.com/security/cve/CVE-2026-50567
suse.com/security/cve/CVE-2026-50568
suse.com/security/cve/CVE-2026-50569
suse.com/security/cve/CVE-2026-50570
suse.com/security/cve/CVE-2026-50879
suse.com/security/cve/CVE-2026-50884
suse.com/security/cve/CVE-2026-50891
suse.com/security/cve/CVE-2026-52855
suse.com/security/cve/CVE-2026-52856
suse.com/security/cve/CVE-2026-52857
suse.com/security/cve/CVE-2026-53469
suse.com/security/cve/CVE-2026-53470
suse.com/security/cve/CVE-2026-53471
suse.com/security/cve/CVE-2026-53474
suse.com/security/cve/CVE-2026-53475
suse.com/security/cve/CVE-2026-53476
suse.com/security/cve/CVE-2026-53551
suse.com/security/cve/CVE-2026-53622
suse.com/security/cve/CVE-2026-53657
suse.com/security/cve/CVE-2026-53658
suse.com/security/cve/CVE-2026-53941
suse.com/security/cve/CVE-2026-54061
suse.com/security/cve/CVE-2026-54162
suse.com/security/cve/CVE-2026-54167
suse.com/security/cve/CVE-2026-54168
suse.com/security/cve/CVE-2026-54245
suse.com/security/cve/CVE-2026-54332
suse.com/security/cve/CVE-2026-54345
suse.com/security/cve/CVE-2026-54523
suse.com/security/cve/CVE-2026-54526
suse.com/security/cve/CVE-2026-54563
suse.com/security/cve/CVE-2026-54572
suse.com/security/cve/CVE-2026-54593
suse.com/security/cve/CVE-2026-54638
suse.com/security/cve/CVE-2026-54650
suse.com/security/cve/CVE-2026-54680
suse.com/security/cve/CVE-2026-54693
suse.com/security/cve/CVE-2026-54719
suse.com/security/cve/CVE-2026-54725
suse.com/security/cve/CVE-2026-54735
suse.com/security/cve/CVE-2026-54763
suse.com/security/cve/CVE-2026-54764
suse.com/security/cve/CVE-2026-54765
suse.com/security/cve/CVE-2026-54787
suse.com/security/cve/CVE-2026-54908
suse.com/security/cve/CVE-2026-54909
suse.com/security/cve/CVE-2026-54910
suse.com/security/cve/CVE-2026-54917
suse.com/security/cve/CVE-2026-55061
suse.com/security/cve/CVE-2026-55062
suse.com/security/cve/CVE-2026-55092
suse.com/security/cve/CVE-2026-55149
suse.com/security/cve/CVE-2026-55477
suse.com/security/cve/CVE-2026-55495
suse.com/security/cve/CVE-2026-55496
suse.com/security/cve/CVE-2026-55497
suse.com/security/cve/CVE-2026-55499
suse.com/security/cve/CVE-2026-55502
suse.com/security/cve/CVE-2026-55580
suse.com/security/cve/CVE-2026-55581
suse.com/security/cve/CVE-2026-55582
suse.com/security/cve/CVE-2026-55637
suse.com/security/cve/CVE-2026-55677
suse.com/security/cve/CVE-2026-56852
suse.com/security/cve/CVE-2026-56853
suse.com/security/cve/CVE-2026-56858
suse.com/security/cve/CVE-2026-56859
suse.com/security/cve/CVE-2026-56860
suse.com/security/cve/CVE-2026-56862
suse.com/security/cve/CVE-2026-56864
suse.com/security/cve/CVE-2026-56865
suse.com/security/cve/CVE-2026-56867
suse.com/security/cve/CVE-2026-56868
suse.com/security/cve/CVE-2026-56869
suse.com/security/cve/CVE-2026-56870
suse.com/security/cve/CVE-2026-56871
suse.com/security/cve/CVE-2026-56872
suse.com/security/cve/CVE-2026-56873
suse.com/security/cve/CVE-2026-56874
suse.com/security/cve/CVE-2026-57210
suse.com/security/cve/CVE-2026-57497
suse.com/security/cve/CVE-2026-59732
suse.com/security/cve/CVE-2026-59733
suse.com/security/cve/CVE-2026-6046
suse.com/security/cve/CVE-2026-61711
suse.com/security/cve/CVE-2026-61712
suse.com/security/cve/CVE-2026-62323
suse.com/security/cve/CVE-2026-62325
suse.com/security/cve/CVE-2026-63328
suse.com/security/cve/CVE-2026-64679
suse.com/security/cve/CVE-2026-64859
suse.com/security/cve/CVE-2026-64863
suse.com/security/cve/CVE-2026-64865
suse.com/security/cve/CVE-2026-64866
suse.com/security/cve/CVE-2026-64868
suse.com/security/cve/CVE-2026-65600
suse.com/security/cve/CVE-2026-65601
suse.com/security/cve/CVE-2026-65602
suse.com/security/cve/CVE-2026-65834
suse.com/security/cve/CVE-2026-65835
suse.com/security/cve/CVE-2026-66063
suse.com/security/cve/CVE-2026-66064
suse.com/security/cve/CVE-2026-6689
suse.com/security/cve/CVE-2026-67309
suse.com/security/cve/CVE-2026-6739
suse.com/security/cve/CVE-2026-67437
suse.com/security/cve/CVE-2026-67438
suse.com/security/cve/CVE-2026-67439
suse.com/security/cve/CVE-2026-67447
suse.com/security/cve/CVE-2026-67448
suse.com/security/cve/CVE-2026-6961
suse.com/security/cve/CVE-2026-71309
suse.com/security/cve/CVE-2026-71310
suse.com/security/cve/CVE-2026-71311
suse.com/security/cve/CVE-2026-71312
suse.com/security/cve/CVE-2026-71313
suse.com/security/cve/CVE-2026-71324
suse.com/security/cve/CVE-2026-71325
suse.com/security/cve/CVE-2026-71326
suse.com/security/cve/CVE-2026-71327
suse.com/security/cve/CVE-2026-71479
suse.com/security/cve/CVE-2026-71556
suse.com/security/cve/CVE-2026-71557
suse.com/security/cve/CVE-2026-7184
suse.com/security/cve/CVE-2026-73080
suse.com/security/cve/CVE-2026-73499
suse.com/security/cve/CVE-2026-73500
suse.com/security/cve/CVE-2026-73502
suse.com/security/cve/CVE-2026-73505
suse.com/security/cve/CVE-2026-73506
suse.com/security/cve/CVE-2026-73509
suse.com/security/cve/CVE-2026-73564
suse.com/security/cve/CVE-2026-7387
suse.com/security/cve/CVE-2026-76905
suse.com/security/cve/CVE-2026-77354
ubuntu.com/security/CVE-2026-59732
cve.org/CVERecord?id=CVE-2026-59732
bugzilla.suse.com/1262438
bugzilla.suse.com/1262439
bugzilla.suse.com/1266210
bugzilla.suse.com/1267192
bugzilla.suse.com/1267869
bugzilla.suse.com/1271056
suse.com/security/cve/CVE-2025-68121
Left out here: 27 references and the rest of 3 source descriptions. The JSON record has them.