CVE-2026-116189: rclone 1.55.0 before 1.75.2 selfupdate Signature Verification Bypass via SHA256SUMS

Published Oct 25, 2026
·
Updated

rclone from 1.55.0 before 1.75.2 contains a signature verification bypass in stable selfupdate that trusts checksums from unsigned bytes preceding the PGP-clearsigned SHA256SUMS block. Attackers controlling the release distribution path can prepend an unsigned checksum line matching a malicious archive, causing selfupdate to install an attacker-controlled rclone executable.

Affected Software

14 affected componentsFixes available
Rclone Rclone>=1.55.0<1.75.2
debian/rclone<=1.60.1+dfsg-2, <=1.60.1+dfsg-4
1.75.2-2
ubuntu/rclone*
ubuntu/rclone*
ubuntu/rclone*
ubuntu/rclone*
ubuntu/rclone*
ubuntu/rclone*
Rclone Rclone>=1.55.0<1.75.2
bitnami/rclone>=1.55.0<1.75.2
1.75.2
alpine/rclone>=1.55.0<1.75.2-r0
1.75.2-r0
debian/rclone*
debian/rclone*
debian/rclone<1.75.2-1
1.75.2-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/rclone to a version that resolves this vulnerability.

    Fixed in 1.75.2-2
  2. Upgrade

    Upgrade bitnami/rclone to a version that resolves this vulnerability.

    Fixed in 1.75.2
  3. Upgrade

    Upgrade alpine/rclone to a version that resolves this vulnerability.

    Fixed in 1.75.2-r0
  4. Upgrade

    Upgrade debian/rclone to a version that resolves this vulnerability.

    Fixed in 1.75.2-1
  5. Upgrade

    Upgrade rclone to a version that resolves this vulnerability.

    Fixed in 1.75.2

Event History

Oct 25, 2026
CVE Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·01:20 PM
Data Sourced
via MITRE·01:20 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 PM
DescriptionSeverityWeaknessAffected Software
Oct 28, 2026
Data Sourced
via OSV·05:50 PM
Affected Software
Oct 29, 2026
Advisory Published
via OSV·08:58 AM

Frequently Asked Questions

1

Which installations are exposed to this issue?

rclone versions from 1.55.0 up to, but not including, 1.75.2 are affected when using the stable selfupdate mechanism. The issue concerns verification of the SHA256SUMS data used during selfupdate.

2

What must an attacker be able to do to exploit it?

An attacker must control the release distribution path used by selfupdate. They can prepend an unsigned checksum for a malicious archive before the PGP-clearsigned SHA256SUMS block, leading selfupdate to accept and install an attacker-controlled executable.

3

Is user interaction required?

Yes. The supplied vector identifies user interaction as required. Exploitation also depends on the affected installation performing a stable selfupdate through an attacker-controlled release distribution path.

4

How can I determine whether a system may be affected?

Check whether the installed rclone version is 1.55.0 or later and earlier than 1.75.2, and whether stable selfupdate is used. Systems that did not use the affected selfupdate path are not described as exposed by the provided information.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203