Synced 03 Aug 2026 05:54 UTC Account
← Rclone

Rclone vulnerabilities: known CVEs & security history

Rclone · Storage / Sync · 6 tracked CVEs · 0 actively exploited · updated August 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all Rclone release lines — 6 in total. A CVE here doesn't mean your version is affected — check Rclone's current status and the safe version to run.

6
known CVEs
0
actively exploited (KEV)
3
critical severity
0
ransomware-linked

Known Rclone CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2026-49980 critical 9.8 1% 2026
CVE-2026-41179 critical 9.8 9% 2026
CVE-2026-41176 critical 9.8 35% 2026
CVE-2026-59733 high 8.8 0% 2026
CVE-2026-54572 high 7.5 0% 2026
CVE-2026-59732 medium 5 0% 2026

Is my Rclone version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your Rclone version → · Monitor Rclone for new CVEs →

Rclone vulnerabilities — frequently asked

How many known vulnerabilities does Rclone have?

IsItPatched tracks 6 CVEs for Rclone. 3 are critical-severity and 2 high-severity. These span every release line — what matters is whether the version you run is affected.

Does Rclone have any actively-exploited vulnerabilities?

None of Rclone's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe Rclone vulnerability?

Among tracked issues, CVE-2026-49980 (CRITICAL, CVSS 9.8) ranks highest — a Missing authentication weakness.

Is Rclone safe to use?

It depends on the version. The latest supported Rclone release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Rclone security status · Rclone end-of-life · actively-exploited CVEs. Always verify against Rclone's advisories — see our disclaimer.