CVE-2026-88046
rclone: source object names can escape the configured root on upload
rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.75.1, rclone core does not reject parent-directory segments in source Object.Remote() values before fs/list, fs/walk, fs/sync, and fs/operations pass those values to destination backends. A flat-keyspace source object store populated with native non-rclone tooling can contain a raw .. key segment, and affected b2, swift, qingstor, oracleobjectstorage, internetarchive, smb, storj, sftp, webdav, ftp, filelu, shade, and sia destinations use path.Join(root, remote) before EncodeDot can neutralize the segment. A copy or upload can therefore escape the configured root into another bucket, share, or path reachable by the victim credential, with sftp and smb potentially reaching other filesystem or share locations under the same login authority. This issue is fixed in version 1.75.1.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- Required
What an attacker can affect
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
5.3
rclone: source object names can escape the configured root on upload
rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.75.1, rclone core does not reject parent-directory segments in source Object.Remote() values before fs/list, fs/walk, fs/sync, and fs/operations pass those values to destination backends. A flat-keyspace source object store populated with native non-rclone tooling can contain a raw .. key segment, and affected b2, swift, qingstor, oracleobjectstorage, internetarchive, smb, storj, sftp, webdav, ftp, filelu, shade, and sia destinations use path.Join(root, remote) before EncodeDot can neutralize the segment. A copy or upload can therefore escape the configured root into another bucket, share, or path reachable by the victim credential, with sftp and smb potentially reaching other filesystem or share locations under the same login authority. This issue is fixed in version 1.75.1.
- Record
CVE-2026-88046- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N - Weakness
- CWE-22
- Updated
- 2026-11-02
EUVDEUVD-2026-75589
5.3
rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.75.1, rclone core does not reject parent-directory segments in source Object.Remote() values before fs/list, fs/walk, fs/sync, and fs/operations pass those values to destination backends. A flat-keyspace source object store populated with native non-rclone tooling can contain a raw .. key segment, and affected b2, swift, qingstor, oracleobjectstorage, internetarchive, smb, storj, sftp, webdav, ftp, filelu, shade, and sia destinations use path.Join(root, remote) before EncodeDot can neutralize the segment. A copy or upload can therefore escape the configured root into another bucket, share, or path reachable by the victim credential, with sftp and smb potentially reaching other filesystem or share locations under the same login authority. This issue is fixed in version 1.75.1.
- Record
EUVD-2026-75589- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-38xv-hf3p-h7mq
5.3
rclone: source object names can escape the configured root on upload
Summary
Multiple backends, when given a specially crafted object to copy, can escape the backend confinement.
| Backend | Keep/Close | Per-backend severity |
|---|---|---|
| sftp | Medium | Real filesystem escape, fires under default encoding. |
| smb | Low-Medium | Escapes to a different SMB share the credential can reach. |
| ftp | Low | Real, leading-.. overshoot PoC is partly neutralized by encoding; escape bounded to at/below the login base. |
| webdav | Low | Server-side ACLs are the real boundary. |
| b2 | Low | Same-account sibling bucket crossing on a flat keyspace. |
| swift | Low | Same, container. |
| qingstor | Low | Same. |
| oracleobjectstorage | Low | Same. |
| internetarchive | Low | IA items are owner-writable only; confined to user's own items. |
| storj | Low | Can retarget a different bucket in the same access grant. |
| filelu | Low | Confined to the user's own account. |
| shade | Low | Confined to the user's own drive. |
| sia | Low | siad API password already grants full-daemon access. |
Root cause
rclone core does not sanitize .. in a source object's Remote() - verified: nothing in fs/march, fs/sync, fs/list, or fs/operations rejects .. segments before the name reaches the destination backend's Put/Update/Mkdir. Confinement is therefore each backend's responsibility, and these backends join root + remote without a check.
This divides into two classes:
-
Bucket based backends -
bucket.Split(path.Join(f.root, rootRelativePath)):backend/b2/b2.go:404,backend/swift/swift.go:464,backend/qingstor/qingstor.go:198,backend/oracleobjectstorage/oracleobjectstorage.go:245,backend/internetarchive/internetarchive.go:1016,backend/smb/smb.go:885,backend/storj/fs.go:289.path.Joincollapses..on the standard (ASCII) form before encoding is applied (e.g.FromStandardPath(path.Join(...))atbackend/b2/b2.go:1641), soEncodeDotnever gets the chance to neutralize the...lib/bucket.Joindoes not clean paths (keeps..as a literal key segment);path.Joindoes.backend/s3,backend/azureblob,backend/googlecloudstoragealready usebucket.Joinand are therefore not affected.
-
Path based backends -
path.Join(root, remote)onto a real path:- sftp:
remotePath = path.Join(f.absRoot, f.opt.Enc.FromStandardPath(remote))(backend/sftp/sftp.go:2497). Default encoding isencoder.Display(==Standard), andFromStandardPathshort-circuits to a pass-through in that mode, so..survives;f.absRootis absolute, sopath.Join("/home/user/root", "../../../../etc/passwd")->/etc/passwd. - webdav:
filePathatbackend/webdav/webdav.go:426-432. - ftp:
path.Join(f.root, remote)at ~14 sites (e.g.backend/ftp/ftp.go:1247). - filelu, shade, sia: analogous joins.
- sftp:
Precondition that limits reachability
For any of these to fire, a source must hand rclone a Remote() containing raw ... That is only possible when:
- the source is a flat-keyspace object store (not a filesystem - a local/sftp/smb source cannot represent
../../xas one directory entry), and - the offending key was written with native, non-rclone tooling - rclone's own writer applies
EncodeDotand rewrites a..segment to fullwidth.., so you cannot create such a key through rclone.
rclone's source-side listing does pass a natively-planted raw .. key through unchanged (verified for b2: remote := file.Name[len(prefix):] after ToStandardPath, backend/b2/b2.go:858,867). The reports never establish this precondition; it is the same omission across every member of the class.
Example attack
# Step 1 - attacker, using NATIVE S3 tooling (NOT rclone) on a source the victim ingests from:
aws s3api put-object --bucket shared-drop --key '../../victim-backups/pwned.txt' --body evil.txt
# Step 2 - victim's ordinary ingest:
rclone copy s3-drop:shared-drop b2:victim-uploads/incoming…
- Record
GHSA-38xv-hf3p-h7mq- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N - Weakness
- CWE-22
- Updated
- 2026-11-02
NVD
5.3
rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.75.1, rclone core does not reject parent-directory segments in source Object.Remote() values before fs/list, fs/walk, fs/sync, and fs/operations pass those values to destination backends. A flat-keyspace source object store populated with native non-rclone tooling can contain a raw .. key segment, and affected b2, swift, qingstor, oracleobjectstorage, internetarchive, smb, storj, sftp, webdav, ftp, filelu, shade, and sia destinations use path.Join(root, remote) before EncodeDot can neutralize the segment. A copy or upload can therefore escape the configured root into another bucket, share, or path reachable by the victim credential, with sftp and smb potentially reaching other filesystem or share locations under the same login authority. This issue is fixed in version 1.75.1.
- Record
CVE-2026-88046- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N - Weakness
- CWE-22
- Updated
- 2026-11-02
OSV
5.3
rclone: source object names can escape the configured root on upload
rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.75.1, rclone core does not reject parent-directory segments in source Object.Remote() values before fs/list, fs/walk, fs/sync, and fs/operations pass those values to destination backends. A flat-keyspace source object store populated with native non-rclone tooling can contain a raw .. key segment, and affected b2, swift, qingstor, oracleobjectstorage, internetarchive, smb, storj, sftp, webdav, ftp, filelu, shade, and sia destinations use path.Join(root, remote) before EncodeDot can neutralize the segment. A copy or upload can therefore escape the configured root into another bucket, share, or path reachable by the victim credential, with sftp and smb potentially reaching other filesystem or share locations under the same login authority. This issue is fixed in version 1.75.1.
- Record
CVE-2026-88046- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N - Weakness
- CWE-22
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2026-88046
5.3
rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.75.1, rclone core does not reject parent-directory segments in source Object.Remote() values before fs/list, fs/walk, fs/sync, and fs/operations pass those values to destination backends. A flat-keyspace source object store populated with native non-rclone tooling can contain a raw .. key segment, and affected b2, swift, qingstor, oracleobjectstorage, internetarchive, smb, storj, sftp, webdav, ftp, filelu, shade, and sia destinations use path.Join(root, remote) before EncodeDot can neutralize the segment. A copy or upload can therefore escape the configured root into another bucket, share, or path reachable by the victim credential, with sftp and smb potentially reaching other filesystem or share locations under the same login authority. This issue is fixed in version 1.75.1.
- Record
DEBIAN-CVE-2026-88046- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N - Updated
- 2026-11-02
Show 7 moreShow less
OSVGHSA-38xv-hf3p-h7mq
5.3
rclone: source object names can escape the configured root on upload
Summary
Multiple backends, when given a specially crafted object to copy, can escape the backend confinement.
| Backend | Keep/Close | Per-backend severity |
|---|---|---|
| sftp | Medium | Real filesystem escape, fires under default encoding. |
| smb | Low-Medium | Escapes to a different SMB share the credential can reach. |
| ftp | Low | Real, leading-.. overshoot PoC is partly neutralized by encoding; escape bounded to at/below the login base. |
| webdav | Low | Server-side ACLs are the real boundary. |
| b2 | Low | Same-account sibling bucket crossing on a flat keyspace. |
| swift | Low | Same, container. |
| qingstor | Low | Same. |
| oracleobjectstorage | Low | Same. |
| internetarchive | Low | IA items are owner-writable only; confined to user's own items. |
| storj | Low | Can retarget a different bucket in the same access grant. |
| filelu | Low | Confined to the user's own account. |
| shade | Low | Confined to the user's own drive. |
| sia | Low | siad API password already grants full-daemon access. |
Root cause
rclone core does not sanitize .. in a source object's Remote() - verified: nothing in fs/march, fs/sync, fs/list, or fs/operations rejects .. segments before the name reaches the destination backend's Put/Update/Mkdir. Confinement is therefore each backend's responsibility, and these backends join root + remote without a check.
This divides into two classes:
-
Bucket based backends -
bucket.Split(path.Join(f.root, rootRelativePath)):backend/b2/b2.go:404,backend/swift/swift.go:464,backend/qingstor/qingstor.go:198,backend/oracleobjectstorage/oracleobjectstorage.go:245,backend/internetarchive/internetarchive.go:1016,backend/smb/smb.go:885,backend/storj/fs.go:289.path.Joincollapses..on the standard (ASCII) form before encoding is applied (e.g.FromStandardPath(path.Join(...))atbackend/b2/b2.go:1641), soEncodeDotnever gets the chance to neutralize the...lib/bucket.Joindoes not clean paths (keeps..as a literal key segment);path.Joindoes.backend/s3,backend/azureblob,backend/googlecloudstoragealready usebucket.Joinand are therefore not affected.
-
Path based backends -
path.Join(root, remote)onto a real path:- sftp:
remotePath = path.Join(f.absRoot, f.opt.Enc.FromStandardPath(remote))(backend/sftp/sftp.go:2497). Default encoding isencoder.Display(==Standard), andFromStandardPathshort-circuits to a pass-through in that mode, so..survives;f.absRootis absolute, sopath.Join("/home/user/root", "../../../../etc/passwd")->/etc/passwd. - webdav:
filePathatbackend/webdav/webdav.go:426-432. - ftp:
path.Join(f.root, remote)at ~14 sites (e.g.backend/ftp/ftp.go:1247). - filelu, shade, sia: analogous joins.
- sftp:
Precondition that limits reachability
For any of these to fire, a source must hand rclone a Remote() containing raw ... That is only possible when:
- the source is a flat-keyspace object store (not a filesystem - a local/sftp/smb source cannot represent
../../xas one directory entry), and - the offending key was written with native, non-rclone tooling - rclone's own writer applies
EncodeDotand rewrites a..segment to fullwidth.., so you cannot create such a key through rclone.
rclone's source-side listing does pass a natively-planted raw .. key through unchanged (verified for b2: remote := file.Name[len(prefix):] after ToStandardPath, backend/b2/b2.go:858,867). The reports never establish this precondition; it is the same omission across every member of the class.
Example attack
# Step 1 - attacker, using NATIVE S3 tooling (NOT rclone) on a source the victim ingests from:
aws s3api put-object --bucket shared-drop --key '../../victim-backups/pwned.txt' --body evil.txt
# Step 2 - victim's ordinary ingest:
rclone copy s3-drop:shared-drop b2:victim-uploads/incoming…
- Record
GHSA-38xv-hf3p-h7mq- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N - Weakness
- CWE-22
- Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-88046
5.3
rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.75.1, rclone core does not reject parent-directory segments in source Object.Remote() values before fs/list, fs/walk, fs/sync, and fs/operations pass those values to destination backends. A flat-keyspace source object store populated with native non-rclone tooling can contain a raw .. key segment, and affected b2, swift, qingstor, oracleobjectstorage, internetarchive, smb, storj, sftp, webdav, ftp, filelu, shade, and sia destinations use path.Join(root, remote) before EncodeDot can neutralize the segment. A copy or upload can therefore escape the configured root into another bucket, share, or path reachable by the victim credential, with sftp and smb potentially reaching other filesystem or share locations under the same login authority. This issue is fixed in version 1.75.1.
- Record
UBUNTU-CVE-2026-88046- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N - Updated
- 2026-11-02
OSVBIT-rclone-2026-88046 No score
rclone: source object names can escape the configured root on upload
rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.75.1, rclone core does not reject parent-directory segments in source Object.Remote() values before fs/list, fs/walk, fs/sync, and fs/operations pass those values to destination backends. A flat-keyspace source object store populated with native non-rclone tooling can contain a raw .. key segment, and affected b2, swift, qingstor, oracleobjectstorage, internetarchive, smb, storj, sftp, webdav, ftp, filelu, shade, and sia destinations use path.Join(root, remote) before EncodeDot can neutralize the segment. A copy or upload can therefore escape the configured root into another bucket, share, or path reachable by the victim credential, with sftp and smb potentially reaching other filesystem or share locations under the same login authority. This issue is fixed in version 1.75.1.
- Record
BIT-rclone-2026-88046- Updated
- 2026-11-02
OSVGO-2026-6457 No score
rclone: source object names can escape the configured root on upload in github.com/rclone/rclone
rclone: source object names can escape the configured root on upload in github.com/rclone/rclone
- Record
GO-2026-6457- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21897-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
Changes for govulncheck-vulndb:
- Update to version 0.0.20260916T180043 2026-09-16T18:00:43Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-6348 CVE-2026-84304 GHSA-vp52-pcj8-j9qc
- GO-2026-6356 CVE-2026-65959 GHSA-mhc4-g3wh-cw7m
- GO-2026-6366 CVE-2026-61625 GHSA-8q3c-rjr9-xxrp
- GO-2026-6372 CVE-2026-79921 GHSA-6c5v-hqjr-5xxp
- GO-2026-6441 CVE-2026-84303 GHSA-qc2q-p7wx-3px3
- GO-2026-6443 CVE-2026-84445 GHSA-2v4p-qf9q-27wj
- GO-2026-6444 CVE-2026-53495 GHSA-7jxh-36q5-gcqv
- GO-2026-6445 CVE-2025-58363 GHSA-c23q-fw86-9h5x
- GO-2026-6446 CVE-2025-24978 GHSA-g8rh-fjm6-h2h9
- GO-2026-6447 CVE-2025-24979 GHSA-pqqc-8v73-9gg2
- GO-2026-6448 CVE-2026-59185 GHSA-cp3j-m783-3ph5
- GO-2026-6449 GHSA-hxjg-93wc-h8p8
- GO-2026-6450 CVE-2026-59172 GHSA-m835-3cm9-rggg
- GO-2026-6451 CVE-2026-59157 GHSA-v25g-mvwr-f5fp
- GO-2026-6452 CVE-2026-59162 GHSA-fx5j-qcqg-grpf
- GO-2026-6453 CVE-2026-59161 GHSA-q5j5-6p94-4gwc
- GO-2026-6454 CVE-2026-88012 GHSA-7ghq-v6jf-g56c
- GO-2026-6455 CVE-2026-88011 GHSA-rf44-j88r-hh8c
- GO-2026-6456 CVE-2026-88045 GHSA-2p48-j3qc-rx9f
- GO-2026-6457 CVE-2026-88046 GHSA-38xv-hf3p-h7mq
- GO-2026-6458 CVE-2026-88017 GHSA-c476-6w5q-jw77
- GO-2026-6459 CVE-2026-88016 GHSA-f8g7-2xjc-7mfh
- GO-2026-6460 CVE-2026-88044 GHSA-p569-5gjg-9cmj
- GO-2026-6461 CVE-2026-88015 GHSA-p6m2-r3w9-mpxw
- GO-2026-6462 CVE-2026-88018 GHSA-xwwr-4h3p-r22c
- GO-2026-6463 CVE-2026-88013 GHSA-486v-q2wf-fp2r
- GO-2026-6464 CVE-2026-88014 GHSA-66hp-wgxq-6f5q
- GO-2026-6465 CVE-2026-88009 GHSA-f52w-8j3h-j724
- GO-2026-6466 CVE-2026-88007 GHSA-qqjf-53cj-pwvv
- GO-2026-6467 CVE-2026-88004 GHSA-v67p-phpq-fc8x
- GO-2026-6468 CVE-2026-88008 GHSA-w4v4-9rw7-5326
- GO-2026-6469 CVE-2026-56665 GHSA-v77h-2w3m-94hx
- GO-2026-6470 CVE-2026-56666 GHSA-992q-9gwp-7r79
- GO-2026-6473 CVE-2026-76081 GHSA-v859-c572-qh5p
- GO-2026-6474 CVE-2026-56668 GHSA-vrh8-c9cm-wh8v
- Update to version 0.0.20260910T144842 2026-09-10T14:48:42Z.
- GO-2026-6302 GHSA-mf7q-r4rv-jv94
- GO-2026-6343 CVE-2026-25782 GHSA-qm72-8prh-g92x
- GO-2026-6344 CVE-2026-26292 GHSA-rc56-rj3f-xggf
- GO-2026-6345 CVE-2026-27779 GHSA-v8f2-2ghq-9whv
- GO-2026-6346 CVE-2026-27780 GHSA-vhq7-fwwh-7hjf
- GO-2026-6347 CVE-2026-27660 GHSA-x92v-f5gc-r34v
- GO-2026-6350 CVE-2026-59832 GHSA-275h-v5h9-vr82
- GO-2026-6351 CVE-2026-72920 GHSA-2v6v-25fm-p4fg
- GO-2026-6353 CVE-2026-59834 GHSA-h89q-4j2h-7h88
- GO-2026-6357 CVE-2026-73667 GHSA-2mw5-23gm-pccq
- GO-2026-6358 CVE-2026-73841 GHSA-52gf-6rpq-fgmx
- GO-2026-6359 CVE-2026-67446 GHSA-75mr-qw9x-3r39
- GO-2026-6360 CVE-2026-73840 GHSA-c5f6-2rm9-2w8g
- GO-2026-6361 CVE-2026-72921 GHSA-gv5w-hfx8-8cwq
- GO-2026-6362 CVE-2026-73843 GHSA-qh9r-j7rp-4x2m
- GO-2026-6363 CVE-2026-67445 GHSA-w878-pj84-3j5v
- GO-2026-6364 GHSA-99rq-75j6-5j9f
- GO-2026-6365 GHSA-gw25-m53r-qh88
- GO-2026-6367 CVE-2026-56743 GHSA-fm8w-2m5w-9j7r
- GO-2026-6368 CVE-2026-75602 GHSA-h6cj-26g5-67fv
- GO-2026-6369 CVE-2026-73232 GHSA-jcvh-xf52-2cwm
- GO-2026-6370 CVE-2026-73292 GHSA-8cj9-r88m-8945
- GO-2026-6371 CVE-2026-73293 GHSA-cxvf-gvfq-36w2
- GO-2026-6373 CVE-2026-69086 GHSA-7hm9-v7vf-7g4w
- GO-2026-6374 CVE-2026-69083 GHSA-fph3-ghq9-vw66
- GO-2026-6377 CVE-2026-69084 GHSA-vh22-h7hf-www7
- GO-2026-6379 CVE-2026-68586 GHSA-36v8-mpjm-8j5r
- GO-2026-6381 CVE-2026-68587 GHSA-69mh-gvh4-8gp7
- GO-2026-6382 CVE-2026-68584 GHSA-7j72-f6wg-cxw6
- GO-2026-6384 CVE-2026-68585 GHSA-pm3w-vxp9-ccwc
- GO-2026-6386 CVE-2026-72809 GHSA-3mp7-4rh5-jrv9
- GO-2026-6387 CVE-2026-72805 GHSA-67x2-mq63-v9vm
- GO-2026-6388 CVE-2026-72806 GHSA-6mcf-g667-w3qv
- GO-2026-6392 CVE-2026-72801 GHSA-8x84-r2ff-h8pq
- GO-2026-6395 CVE-2026-72800 GHSA-5fhr-f75j-8wr9
- GO-2026-6398 CVE-2026-72802 GHSA-jv8v-xq2h-657v
- GO-2026-6400 CVE-2026-72810 GHSA-mw8r-mw84-88v2
- GO-2026-6402 CVE-2026-72811 GHSA-q2vg-7qgx-x5fc
- GO-2026-6404 CVE-2026-72803…
- Record
openSUSE-SU-2026:21897-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:23855-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
Changes for govulncheck-vulndb:
- Update to version 0.0.20260916T180043 2026-09-16T18:00:43Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-6348 CVE-2026-84304 GHSA-vp52-pcj8-j9qc
- GO-2026-6356 CVE-2026-65959 GHSA-mhc4-g3wh-cw7m
- GO-2026-6366 CVE-2026-61625 GHSA-8q3c-rjr9-xxrp
- GO-2026-6372 CVE-2026-79921 GHSA-6c5v-hqjr-5xxp
- GO-2026-6441 CVE-2026-84303 GHSA-qc2q-p7wx-3px3
- GO-2026-6443 CVE-2026-84445 GHSA-2v4p-qf9q-27wj
- GO-2026-6444 CVE-2026-53495 GHSA-7jxh-36q5-gcqv
- GO-2026-6445 CVE-2025-58363 GHSA-c23q-fw86-9h5x
- GO-2026-6446 CVE-2025-24978 GHSA-g8rh-fjm6-h2h9
- GO-2026-6447 CVE-2025-24979 GHSA-pqqc-8v73-9gg2
- GO-2026-6448 CVE-2026-59185 GHSA-cp3j-m783-3ph5
- GO-2026-6449 GHSA-hxjg-93wc-h8p8
- GO-2026-6450 CVE-2026-59172 GHSA-m835-3cm9-rggg
- GO-2026-6451 CVE-2026-59157 GHSA-v25g-mvwr-f5fp
- GO-2026-6452 CVE-2026-59162 GHSA-fx5j-qcqg-grpf
- GO-2026-6453 CVE-2026-59161 GHSA-q5j5-6p94-4gwc
- GO-2026-6454 CVE-2026-88012 GHSA-7ghq-v6jf-g56c
- GO-2026-6455 CVE-2026-88011 GHSA-rf44-j88r-hh8c
- GO-2026-6456 CVE-2026-88045 GHSA-2p48-j3qc-rx9f
- GO-2026-6457 CVE-2026-88046 GHSA-38xv-hf3p-h7mq
- GO-2026-6458 CVE-2026-88017 GHSA-c476-6w5q-jw77
- GO-2026-6459 CVE-2026-88016 GHSA-f8g7-2xjc-7mfh
- GO-2026-6460 CVE-2026-88044 GHSA-p569-5gjg-9cmj
- GO-2026-6461 CVE-2026-88015 GHSA-p6m2-r3w9-mpxw
- GO-2026-6462 CVE-2026-88018 GHSA-xwwr-4h3p-r22c
- GO-2026-6463 CVE-2026-88013 GHSA-486v-q2wf-fp2r
- GO-2026-6464 CVE-2026-88014 GHSA-66hp-wgxq-6f5q
- GO-2026-6465 CVE-2026-88009 GHSA-f52w-8j3h-j724
- GO-2026-6466 CVE-2026-88007 GHSA-qqjf-53cj-pwvv
- GO-2026-6467 CVE-2026-88004 GHSA-v67p-phpq-fc8x
- GO-2026-6468 CVE-2026-88008 GHSA-w4v4-9rw7-5326
- GO-2026-6469 CVE-2026-56665 GHSA-v77h-2w3m-94hx
- GO-2026-6470 CVE-2026-56666 GHSA-992q-9gwp-7r79
- GO-2026-6473 CVE-2026-76081 GHSA-v859-c572-qh5p
- GO-2026-6474 CVE-2026-56668 GHSA-vrh8-c9cm-wh8v
- Update to version 0.0.20260910T144842 2026-09-10T14:48:42Z.
- GO-2026-6302 GHSA-mf7q-r4rv-jv94
- GO-2026-6343 CVE-2026-25782 GHSA-qm72-8prh-g92x
- GO-2026-6344 CVE-2026-26292 GHSA-rc56-rj3f-xggf
- GO-2026-6345 CVE-2026-27779 GHSA-v8f2-2ghq-9whv
- GO-2026-6346 CVE-2026-27780 GHSA-vhq7-fwwh-7hjf
- GO-2026-6347 CVE-2026-27660 GHSA-x92v-f5gc-r34v
- GO-2026-6350 CVE-2026-59832 GHSA-275h-v5h9-vr82
- GO-2026-6351 CVE-2026-72920 GHSA-2v6v-25fm-p4fg
- GO-2026-6353 CVE-2026-59834 GHSA-h89q-4j2h-7h88
- GO-2026-6357 CVE-2026-73667 GHSA-2mw5-23gm-pccq
- GO-2026-6358 CVE-2026-73841 GHSA-52gf-6rpq-fgmx
- GO-2026-6359 CVE-2026-67446 GHSA-75mr-qw9x-3r39
- GO-2026-6360 CVE-2026-73840 GHSA-c5f6-2rm9-2w8g
- GO-2026-6361 CVE-2026-72921 GHSA-gv5w-hfx8-8cwq
- GO-2026-6362 CVE-2026-73843 GHSA-qh9r-j7rp-4x2m
- GO-2026-6363 CVE-2026-67445 GHSA-w878-pj84-3j5v
- GO-2026-6364 GHSA-99rq-75j6-5j9f
- GO-2026-6365 GHSA-gw25-m53r-qh88
- GO-2026-6367 CVE-2026-56743 GHSA-fm8w-2m5w-9j7r
- GO-2026-6368 CVE-2026-75602 GHSA-h6cj-26g5-67fv
- GO-2026-6369 CVE-2026-73232 GHSA-jcvh-xf52-2cwm
- GO-2026-6370 CVE-2026-73292 GHSA-8cj9-r88m-8945
- GO-2026-6371 CVE-2026-73293 GHSA-cxvf-gvfq-36w2
- GO-2026-6373 CVE-2026-69086 GHSA-7hm9-v7vf-7g4w
- GO-2026-6374 CVE-2026-69083 GHSA-fph3-ghq9-vw66
- GO-2026-6377 CVE-2026-69084 GHSA-vh22-h7hf-www7
- GO-2026-6379 CVE-2026-68586 GHSA-36v8-mpjm-8j5r
- GO-2026-6381 CVE-2026-68587 GHSA-69mh-gvh4-8gp7
- GO-2026-6382 CVE-2026-68584 GHSA-7j72-f6wg-cxw6
- GO-2026-6384 CVE-2026-68585 GHSA-pm3w-vxp9-ccwc
- GO-2026-6386 CVE-2026-72809 GHSA-3mp7-4rh5-jrv9
- GO-2026-6387 CVE-2026-72805 GHSA-67x2-mq63-v9vm
- GO-2026-6388 CVE-2026-72806 GHSA-6mcf-g667-w3qv
- GO-2026-6392 CVE-2026-72801 GHSA-8x84-r2ff-h8pq
- GO-2026-6395 CVE-2026-72800 GHSA-5fhr-f75j-8wr9
- GO-2026-6398 CVE-2026-72802 GHSA-jv8v-xq2h-657v
- GO-2026-6400 CVE-2026-72810 GHSA-mw8r-mw84-88v2
- GO-2026-6402 CVE-2026-72811 GHSA-q2vg-7qgx-x5fc
- GO-2026-6404 CVE-2026-72803…
- Record
SUSE-SU-2026:23855-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:23863-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
Changes for govulncheck-vulndb:
- Update to version 0.0.20260916T180043 2026-09-16T18:00:43Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-6348 CVE-2026-84304 GHSA-vp52-pcj8-j9qc
- GO-2026-6356 CVE-2026-65959 GHSA-mhc4-g3wh-cw7m
- GO-2026-6366 CVE-2026-61625 GHSA-8q3c-rjr9-xxrp
- GO-2026-6372 CVE-2026-79921 GHSA-6c5v-hqjr-5xxp
- GO-2026-6441 CVE-2026-84303 GHSA-qc2q-p7wx-3px3
- GO-2026-6443 CVE-2026-84445 GHSA-2v4p-qf9q-27wj
- GO-2026-6444 CVE-2026-53495 GHSA-7jxh-36q5-gcqv
- GO-2026-6445 CVE-2025-58363 GHSA-c23q-fw86-9h5x
- GO-2026-6446 CVE-2025-24978 GHSA-g8rh-fjm6-h2h9
- GO-2026-6447 CVE-2025-24979 GHSA-pqqc-8v73-9gg2
- GO-2026-6448 CVE-2026-59185 GHSA-cp3j-m783-3ph5
- GO-2026-6449 GHSA-hxjg-93wc-h8p8
- GO-2026-6450 CVE-2026-59172 GHSA-m835-3cm9-rggg
- GO-2026-6451 CVE-2026-59157 GHSA-v25g-mvwr-f5fp
- GO-2026-6452 CVE-2026-59162 GHSA-fx5j-qcqg-grpf
- GO-2026-6453 CVE-2026-59161 GHSA-q5j5-6p94-4gwc
- GO-2026-6454 CVE-2026-88012 GHSA-7ghq-v6jf-g56c
- GO-2026-6455 CVE-2026-88011 GHSA-rf44-j88r-hh8c
- GO-2026-6456 CVE-2026-88045 GHSA-2p48-j3qc-rx9f
- GO-2026-6457 CVE-2026-88046 GHSA-38xv-hf3p-h7mq
- GO-2026-6458 CVE-2026-88017 GHSA-c476-6w5q-jw77
- GO-2026-6459 CVE-2026-88016 GHSA-f8g7-2xjc-7mfh
- GO-2026-6460 CVE-2026-88044 GHSA-p569-5gjg-9cmj
- GO-2026-6461 CVE-2026-88015 GHSA-p6m2-r3w9-mpxw
- GO-2026-6462 CVE-2026-88018 GHSA-xwwr-4h3p-r22c
- GO-2026-6463 CVE-2026-88013 GHSA-486v-q2wf-fp2r
- GO-2026-6464 CVE-2026-88014 GHSA-66hp-wgxq-6f5q
- GO-2026-6465 CVE-2026-88009 GHSA-f52w-8j3h-j724
- GO-2026-6466 CVE-2026-88007 GHSA-qqjf-53cj-pwvv
- GO-2026-6467 CVE-2026-88004 GHSA-v67p-phpq-fc8x
- GO-2026-6468 CVE-2026-88008 GHSA-w4v4-9rw7-5326
- GO-2026-6469 CVE-2026-56665 GHSA-v77h-2w3m-94hx
- GO-2026-6470 CVE-2026-56666 GHSA-992q-9gwp-7r79
- GO-2026-6473 CVE-2026-76081 GHSA-v859-c572-qh5p
- GO-2026-6474 CVE-2026-56668 GHSA-vrh8-c9cm-wh8v
- Update to version 0.0.20260910T144842 2026-09-10T14:48:42Z.
- GO-2026-6302 GHSA-mf7q-r4rv-jv94
- GO-2026-6343 CVE-2026-25782 GHSA-qm72-8prh-g92x
- GO-2026-6344 CVE-2026-26292 GHSA-rc56-rj3f-xggf
- GO-2026-6345 CVE-2026-27779 GHSA-v8f2-2ghq-9whv
- GO-2026-6346 CVE-2026-27780 GHSA-vhq7-fwwh-7hjf
- GO-2026-6347 CVE-2026-27660 GHSA-x92v-f5gc-r34v
- GO-2026-6350 CVE-2026-59832 GHSA-275h-v5h9-vr82
- GO-2026-6351 CVE-2026-72920 GHSA-2v6v-25fm-p4fg
- GO-2026-6353 CVE-2026-59834 GHSA-h89q-4j2h-7h88
- GO-2026-6357 CVE-2026-73667 GHSA-2mw5-23gm-pccq
- GO-2026-6358 CVE-2026-73841 GHSA-52gf-6rpq-fgmx
- GO-2026-6359 CVE-2026-67446 GHSA-75mr-qw9x-3r39
- GO-2026-6360 CVE-2026-73840 GHSA-c5f6-2rm9-2w8g
- GO-2026-6361 CVE-2026-72921 GHSA-gv5w-hfx8-8cwq
- GO-2026-6362 CVE-2026-73843 GHSA-qh9r-j7rp-4x2m
- GO-2026-6363 CVE-2026-67445 GHSA-w878-pj84-3j5v
- GO-2026-6364 GHSA-99rq-75j6-5j9f
- GO-2026-6365 GHSA-gw25-m53r-qh88
- GO-2026-6367 CVE-2026-56743 GHSA-fm8w-2m5w-9j7r
- GO-2026-6368 CVE-2026-75602 GHSA-h6cj-26g5-67fv
- GO-2026-6369 CVE-2026-73232 GHSA-jcvh-xf52-2cwm
- GO-2026-6370 CVE-2026-73292 GHSA-8cj9-r88m-8945
- GO-2026-6371 CVE-2026-73293 GHSA-cxvf-gvfq-36w2
- GO-2026-6373 CVE-2026-69086 GHSA-7hm9-v7vf-7g4w
- GO-2026-6374 CVE-2026-69083 GHSA-fph3-ghq9-vw66
- GO-2026-6377 CVE-2026-69084 GHSA-vh22-h7hf-www7
- GO-2026-6379 CVE-2026-68586 GHSA-36v8-mpjm-8j5r
- GO-2026-6381 CVE-2026-68587 GHSA-69mh-gvh4-8gp7
- GO-2026-6382 CVE-2026-68584 GHSA-7j72-f6wg-cxw6
- GO-2026-6384 CVE-2026-68585 GHSA-pm3w-vxp9-ccwc
- GO-2026-6386 CVE-2026-72809 GHSA-3mp7-4rh5-jrv9
- GO-2026-6387 CVE-2026-72805 GHSA-67x2-mq63-v9vm
- GO-2026-6388 CVE-2026-72806 GHSA-6mcf-g667-w3qv
- GO-2026-6392 CVE-2026-72801 GHSA-8x84-r2ff-h8pq
- GO-2026-6395 CVE-2026-72800 GHSA-5fhr-f75j-8wr9
- GO-2026-6398 CVE-2026-72802 GHSA-jv8v-xq2h-657v
- GO-2026-6400 CVE-2026-72810 GHSA-mw8r-mw84-88v2
- GO-2026-6402 CVE-2026-72811 GHSA-q2vg-7qgx-x5fc
- GO-2026-6404 CVE-2026-72803…
- Record
SUSE-SU-2026:23863-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/rclone/rcloneGo |
before 1.75.1 | 1.75.1 |
rcloneBitnami |
before 1.75.1 | 1.75.1 |
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 |
govulncheck-vulndbSUSE:Linux Enterprise Server 16.0 From an advisory covering 91 CVEs |
before 0.0.20260916T180043-160000.1.1 | 0.0.20260916T180043-160000.1.1 |
govulncheck-vulndbSUSE:Linux Enterprise Server for SAP applications 16.0 From an advisory covering 91 CVEs |
before 0.0.20260916T180043-160000.1.1 | 0.0.20260916T180043-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 |
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 |
govulncheck-vulndbopenSUSE:Leap 16.0 From an advisory covering 91 CVEs |
before 0.0.20260916T180043-160000.1.1 | 0.0.20260916T180043-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-88046 is a medium vulnerability (CVSS 5.3) in Rclone, published September 10, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.29%, the 22nd percentile. Fixed in github.com/rclone/rclone 1.75.1.
References
github.com/rclone/rclone/security/advisories/GHSA-38xv-hf3p-h7mq
github.com/rclone/rclone/commit/57842c5ee4e1407eda06a414a36510cce2db4252
github.com/rclone/rclone/releases/tag/v1.75.1
nvd.nist.gov/vuln/detail/CVE-2026-88046
github.com/advisories/GHSA-38xv-hf3p-h7mq
github.com/CVEProject/cvelistV5/tree/main/cves/2026/88xxx/CVE-2026-88046.json
Show 97 moreShow less
security-tracker.debian.org/tracker/CVE-2026-88046
github.com/rclone/rclone
suse.com/support/update/announcement/2026/suse-su-202623855-1
suse.com/security/cve/CVE-2025-24978
suse.com/security/cve/CVE-2025-24979
suse.com/security/cve/CVE-2025-58363
suse.com/security/cve/CVE-2026-11720
suse.com/security/cve/CVE-2026-25782
suse.com/security/cve/CVE-2026-26292
suse.com/security/cve/CVE-2026-27660
suse.com/security/cve/CVE-2026-27779
suse.com/security/cve/CVE-2026-27780
suse.com/security/cve/CVE-2026-53495
suse.com/security/cve/CVE-2026-56665
suse.com/security/cve/CVE-2026-56666
suse.com/security/cve/CVE-2026-56668
suse.com/security/cve/CVE-2026-56743
suse.com/security/cve/CVE-2026-59157
suse.com/security/cve/CVE-2026-59161
suse.com/security/cve/CVE-2026-59162
suse.com/security/cve/CVE-2026-59172
suse.com/security/cve/CVE-2026-59185
suse.com/security/cve/CVE-2026-59832
suse.com/security/cve/CVE-2026-59834
suse.com/security/cve/CVE-2026-60004
suse.com/security/cve/CVE-2026-61625
suse.com/security/cve/CVE-2026-65959
suse.com/security/cve/CVE-2026-67445
suse.com/security/cve/CVE-2026-67446
suse.com/security/cve/CVE-2026-68584
suse.com/security/cve/CVE-2026-68585
suse.com/security/cve/CVE-2026-68586
suse.com/security/cve/CVE-2026-68587
suse.com/security/cve/CVE-2026-69083
suse.com/security/cve/CVE-2026-69084
suse.com/security/cve/CVE-2026-69086
suse.com/security/cve/CVE-2026-71493
suse.com/security/cve/CVE-2026-71494
suse.com/security/cve/CVE-2026-72789
suse.com/security/cve/CVE-2026-72790
suse.com/security/cve/CVE-2026-72792
suse.com/security/cve/CVE-2026-72793
suse.com/security/cve/CVE-2026-72794
suse.com/security/cve/CVE-2026-72795
suse.com/security/cve/CVE-2026-72796
suse.com/security/cve/CVE-2026-72797
suse.com/security/cve/CVE-2026-72798
suse.com/security/cve/CVE-2026-72799
suse.com/security/cve/CVE-2026-72800
suse.com/security/cve/CVE-2026-72801
suse.com/security/cve/CVE-2026-72802
suse.com/security/cve/CVE-2026-72803
suse.com/security/cve/CVE-2026-72804
suse.com/security/cve/CVE-2026-72805
suse.com/security/cve/CVE-2026-72806
suse.com/security/cve/CVE-2026-72807
suse.com/security/cve/CVE-2026-72808
suse.com/security/cve/CVE-2026-72809
suse.com/security/cve/CVE-2026-72810
suse.com/security/cve/CVE-2026-72811
suse.com/security/cve/CVE-2026-72812
suse.com/security/cve/CVE-2026-72920
suse.com/security/cve/CVE-2026-72921
suse.com/security/cve/CVE-2026-73087
suse.com/security/cve/CVE-2026-73232
suse.com/security/cve/CVE-2026-73292
suse.com/security/cve/CVE-2026-73293
suse.com/security/cve/CVE-2026-73294
suse.com/security/cve/CVE-2026-73667
suse.com/security/cve/CVE-2026-73840
suse.com/security/cve/CVE-2026-73841
suse.com/security/cve/CVE-2026-73842
suse.com/security/cve/CVE-2026-73843
suse.com/security/cve/CVE-2026-75602
suse.com/security/cve/CVE-2026-76081
suse.com/security/cve/CVE-2026-79921
suse.com/security/cve/CVE-2026-84303
suse.com/security/cve/CVE-2026-84304
suse.com/security/cve/CVE-2026-84445
suse.com/security/cve/CVE-2026-88004
suse.com/security/cve/CVE-2026-88007
suse.com/security/cve/CVE-2026-88008
suse.com/security/cve/CVE-2026-88009
suse.com/security/cve/CVE-2026-88011
suse.com/security/cve/CVE-2026-88012
suse.com/security/cve/CVE-2026-88013
suse.com/security/cve/CVE-2026-88014
suse.com/security/cve/CVE-2026-88015
suse.com/security/cve/CVE-2026-88016
suse.com/security/cve/CVE-2026-88017
suse.com/security/cve/CVE-2026-88018
suse.com/security/cve/CVE-2026-88044
suse.com/security/cve/CVE-2026-88045
suse.com/security/cve/CVE-2026-88046
suse.com/support/update/announcement/2026/suse-su-202623863-1
ubuntu.com/security/CVE-2026-88046
cve.org/CVERecord?id=CVE-2026-88046
Left out here: the rest of 5 source descriptions. The JSON record has them.