Skip to main content
Menu
CVEs

Rclone auth token leak via Ulozto backend redirect

Only affects rclone 1.67.0 up to 1.76.0 when the Ulozto backend is configured (type = ulozto). Fixed in 1.76.0.

CVE-2026-134350Published November 21, 2026, updated

6.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 1.76.0
Who is exposed
Not reported

Summary

Written by a model

rclone 1.67.0 before 1.76.0 contains a credential leak vulnerability in the Ulozto backend that sends X-Auth-Token and X-User-Token headers to unintended hosts on HTTP redirect because downloads use the authenticated f.rest client instead of f.cdn. Attackers who can observe or redirect CDN download traffic can capture the long-lived API key and session token to gain persistent access to the victim's Ulozto storage.

Who should check

Teams running rclone 1.67.0 through 1.75.x with the Ulozto backend configured (type = ulozto) for downloads.

“rclone 1.67.0 before 1.76.0 contains a credential leak vulnerability in the Ulozto backend”

vulncheck.com

What to do

Upgrade to a fixed version: 1.76.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134350 (rclone 1.67.0 before 1.76.0 Auth Token Leak via Ulozto Backend Redirect), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134350 (entry last updated 2026-11-21):
Affected:
- Go package github.com/rclone/rclone: from 1.67.0, fixed in 1.76.0
Fixed versions: 1.76.0.
Conditions (all must be true for the bug to be hit):
- rclone version 1.67.0 up to (not including) 1.76.0 (source: https://www.vulncheck.com/advisories/rclone-1.67.0-before-1.76.0-auth-token-leak-via-ulozto-backend-redirect)
- The Ulozto backend is configured in rclone (type = ulozto) (source: https://github.com/rclone/rclone/security/advisories/GHSA-3xpx-hjg2-vrjh)
- Victim downloads files through the Ulozto backend, which triggers the vulnerable download path (source: https://github.com/rclone/rclone/security/advisories/GHSA-3xpx-hjg2-vrjh)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134350 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134350 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/rclone/rclone/security/advisories/GHSA-3xpx-hjg2-vrjh
- https://www.vulncheck.com/advisories/rclone-1.67.0-before-1.76.0-auth-token-leak-via-ulozto-backend-redirect
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134350
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134350"}.

Affected versions

cve.now Index

33Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach10/20Affects Go packages
  • Severity6.3/10CVSS 6.3
  • No patch0/5No signal

What would change the score

  • Would score about 78 if added to CISA KEV
  • Would score about 73 if CISA's SSVC rates exploitation active
  • Would score about 38 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · rclone/rclone · Advisory GHSA-3xpx-hjg2-vrjh
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134350
RecordNVD · CVE-2026-134350
Other links 1
Linkvulncheck.com · advisories/rclone-1.67.0-before-1.76.0-auth-token-leak-via-ulozto-backend-redirect

Questions about CVE-2026-134350

Is CVE-2026-134350 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

Downloading files through the Ulozto backend can leak an auth token. An attacker could then gain persistent API access and session-level access to the victim's Ulozto storage.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134350?

github.com/rclone/rclone (Go): from 1.67.0 before 1.76.0.

Source: cve.now feed data

Am I affected, and how do I check?

Versions from 1.67.0 up to but not including 1.76.0 are affected, but only when the Ulozto backend is configured with type = ulozto. Check the installed version with rclone version and search the rclone config file for a remote with type = ulozto.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134350?

Upgrade rclone to 1.76.0 or later.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.