CVE-2025-68121VulnerabilityPublished 22 Jul 2026Updated 10 Nov 2026

SUSE · Security update for rclone

Affects SUSESource GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2025-68121· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical · fixed in SUSE package updates : patch SUSE tls as a priority.

Data as of 10 Nov 2026, 20:06 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 1.26.0-rc.3, 1.25.7, 1.24.13

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade crypto/tls to 1.26.0-rc.3, 1.25.7 or 1.24.13.

Affected software

Product	Affected	Fixed in
Go standard librarycrypto/tls	Affected >=1.26.0-rc.1 <1.26.0-rc.3	Fixed in 1.26.0-rc.3
Go standard librarycrypto/tls	Affected >=1.25.0-0 <1.25.7	Fixed in 1.25.7
Go standard librarycrypto/tls	Affected <1.24.13	Fixed in 1.24.13
Gocrypto/tls`pkg:golang/crypto/tls`Other threats	Affected <1.24.13 >=1.25.0-0 <1.25.7 >=1.26.0-rc.1 <1.26.0-rc.3	Fixed in 1.24.13 1.25.7 1.26.0-rc.3
Gogithub.com/golang/go/src/crypto/tls`pkg:golang/github.com/golang/go/src/crypto/tls`Other threats	Affected =0 =1.25.0-0 =1.26.0-rc.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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 candidate hostname only once - log: Fix wrong source file:line in JSON logs from release builds (Nick Craig-Wood) - mount2: Fix empty directory listings on re-read (Janne Beate Bakeng) - serve s3: Fix multipart ListParts pagination returning wrong part numbers (Nick Craig-Wood) - serve sftp - Fix file corruption when a client resumes an upload (Nick Craig-Wood) - Fix truncate request being silently ignored (Nick Craig-Wood) - Local - Fix getXattr returning empty map instead of nil (Leon Brocard) - Drime - Fix server-side copy and move failing with Cloudflare 520 error (Nick Craig-Wood) - Fix files being uploaded to the wrong directory (Nick Craig-Wood) - Remove duplicate upload_cutoff config option (Nick Craig-Wood) - Fix directory rename leaving the renamed folder empty in VFS (Nick Craig-Wood) - Drive - Fix server-side move failing on shared drives with du

GCVE source: db.gcve.eu
Csaf Category: csaf_security_advisory
Csaf Version: 2.0
Publisher: SUSE Product Security Team
Advisory ID: openSUSE-SU-2026:21436-1
Vendor Severity: critical
CVE Count: 37
Additional Cves: CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-27141, CVE-2026-27145, CVE-2026-32952, CVE-2026-33809, CVE-2026-33813, CVE-2026-33814, CVE-2026-39821, CVE-2026-39824, CVE-2026-39827, CVE-2026-39828, CVE-2026-39829, CVE-2026-39830, CVE-2026-39831, CVE-2026-39832, CVE-2026-39833, CVE-2026-39834, CVE-2026-39835, CVE-2026-41176, CVE-2026-41179, CVE-2026-42500, CVE-2026-42502, CVE-2026-42504, CVE-2026-42506, CVE-2026-42507, CVE-2026-42508, CVE-2026-44740, CVE-2026-46595, CVE-2026-46597, CVE-2026-46598, CVE-2026-49980, CVE-2026-54572, CVE-2026-59732, CVE-2026-59733

References

Community reviews

Loading reviews…