Skip to main content
Menu
CVEs

Rclone auth bypass in cached auth-proxy credentials

Only affects rclone 1.49.0 through 1.75.x using an auth proxy (--auth-proxy) with serve sftp, ftp, http or webdav. Fixed in 1.76.0.

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

2.3LowCNA
Exploited
No known exploitation
Fix
Fixed in 1.76.0
Who is exposed
Specific setups only

Summary

Written by a model

Rclone 1.49.0 before 1.76.0 contains an improper authentication vulnerability in Proxy.Call that lets revoked users keep access because cached auth-proxy answers are never revalidated. Revoked users of serve sftp, ftp, http, or webdav can reconnect within five minutes using their original credentials to retain access indefinitely.

Who should check

Teams running rclone 1.49.0 through 1.75.x with serve sftp, ftp, http or webdav behind an --auth-proxy, where access revocation matters

“Proxy.Call , used by serve sftp , ftp , http and webdav”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Uses an auth proxy (--auth-proxy) with rclone serve sftp, ftp, http or webdav Affects rclone 1.49.0 up to, but not including, 1.76.0
  2. 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-134351 (Rclone 1.49.0 before 1.76.0 Auth-Proxy Revocation Bypass via Cached Credentials), 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-134351 (entry last updated 2026-11-21):
Affected:
- Go package github.com/rclone/rclone: from 1.49.0, fixed in 1.76.0
Fixed versions: 1.76.0.
Conditions (all must be true for the bug to be hit):
- Uses an auth proxy (--auth-proxy) with rclone serve sftp, ftp, http or webdav (source: https://github.com/rclone/rclone/security/advisories/GHSA-vmgx-g9c5-669p)
- Affects rclone 1.49.0 up to, but not including, 1.76.0 (source: https://www.vulncheck.com/advisories/rclone-1.49.0-before-1.76.0-auth-proxy-revocation-bypass-via-cached-credentials)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134351 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134351 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-vmgx-g9c5-669p
- https://www.vulncheck.com/advisories/rclone-1.49.0-before-1.76.0-auth-proxy-revocation-bypass-via-cached-credentials
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-134351
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-134351"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Go packages
  • Severity2.3/10CVSS 2.3
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 27 if CISA's SSVC rates it automatable

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-vmgx-g9c5-669p
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134351
RecordNVD · CVE-2026-134351
Other links 1
Linkvulncheck.com · advisories/rclone-1.49.0-before-1.76.0-auth-proxy-revocation-bypass-via-cached-credentials

Questions about CVE-2026-134351

Is CVE-2026-134351 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?

A user whose access has been revoked can reconnect within five minutes using their original credentials and keep access indefinitely, so revocation does not cut them off.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-134351?

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

Source: cve.now feed data

Am I affected, and how do I check?

Affects rclone 1.49.0 up to, but not including, 1.76.0, and only when the server runs with an auth proxy (--auth-proxy) for serve sftp, ftp, http or webdav. To check, run rclone version for the release and look for the --auth-proxy option in the serve command's configuration.

Source: github.com, vulncheck.com

How do I fix CVE-2026-134351?

Upgrade to rclone 1.76.0 or later, which is the listed fixed version.

Source: github.com, vulncheck.com

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