Skip to main content
CVE-2026-134350VulnerabilityPublished

rclone 1.67.0 before 1.76.0 contains a credential leak vulnerability in the Ulozto backend that sends X-Auth-Token and

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134350· Medium 6.3

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

Data as of 21 Nov 2026, 19:44 UTC

CVSS 4.0 base score
6.3Medium
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.3
CNA (VulnCheck)CVSS 3.14.8
Patch
Available – fixed in 1.76.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/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 21 Nov 2026.

What to do

Upgrade rclone to 1.76.0.

Affected software

ProductAffectedFixed in
rclonercloneAffected
  • >=1.67.0 <1.76.0
Fixed in
  • 1.76.0
Gorclonepkg:golang/rcloneOther threatsAffected
  • >=1.67.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

A fix is available in rclone version 1.76.0 and later. Users should upgrade to version 1.76.0 or newer to remediate this vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

rclone versions from 1.67.0 up to but not including 1.76.0 have a vulnerability in the Ulozto backend where authentication tokens (X-Auth-Token and X-User-Token) are sent to unintended hosts during HTTP redirects. This occurs because the downloads use the authenticated f.rest client instead of the f.cdn client, potentially exposing long-lived API keys and session tokens to attackers who can observe or redirect CDN traffic.

References

Community reviews

Loading reviews…