Skip to main content
VulnerabilityPublished

CVE-2026-134348: rclone · Timing Side Channel

Affects rcloneSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.76.0 when convenient.

Data as of 21 Nov 2026, 17:15 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.9
CNA (VulnCheck)CVSS 3.15.3
Patch
Available – fixed in 1.76.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 20 Nov 2026.

What to do

Upgrade rclone to 1.76.0.

Affected software

ProductAffectedFixed in
rclonercloneAffected
  • >=1.56.0 <1.76.0
Fixed in
  • 1.76.0
Gorclonepkg:golang/rcloneOther threatsAffected
  • >=1.56.0 <1.76.0
Fixed in
  • 1.76.0

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

AI-suggested

Upgrade rclone to version 1.76.0 or later, where this timing side-channel vulnerability has been fixed. No other mitigations are specified or required.

Description

Rclone versions from 1.56.0 up to but not including 1.76.0 have a timing side-channel vulnerability in the htpasswd authentication middleware. This flaw allows unauthenticated attackers to enumerate valid usernames by sending HTTP Basic Auth requests with incorrect passwords and measuring response times. The vulnerability arises because bcrypt verification is only performed for existing users, causing observable timing discrepancies. The issue is fixed in version 1.76.0.

References

Community reviews

Loading reviews…