Skip to main content
Menu
CVEs

Rclone authentication bypass in serve sftp auth-proxy cache

Affects rclone 1.51.0 before 1.76.0 when serve sftp runs with --auth-proxy. Fixed in 1.76.0.

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

9.2CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 1.76.0
Who is exposed
Specific setups only

Summary

Written by a model

Rclone from 1.51.0 before 1.76.0 contains an authentication bypass vulnerability in serve sftp --auth-proxy because the generateCacheKey cache key omits the authentication method. Attackers knowing a victim's base64 public key can submit it as a password from the same client IP to reuse the cached entry and gain read-write VFS access.

Who should check

Anyone running rclone 1.51.0 through 1.76.0 with serve sftp and --auth-proxy, including shared-IP setups behind NAT, bastions or load balancers.

Not fixed by: Key-only auth policies do not stop the password path.

“serve sftp with --auth-proxy , the only affected server”

github.com

What to do

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

    Uses rclone serve sftp with --auth-proxy The proxy handles public key and password logins differently The victim's cached key entry is still within its lifetime Attacker connects from the same client IP as the victim, same username; not a unix socket
  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-134352 (Rclone 1.51.0 before 1.76.0 Authentication Bypass via serve sftp Auth-Proxy Cache), 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-134352 (entry last updated 2026-11-21):
Affected:
- Go package github.com/rclone/rclone: from 1.51.0, fixed in 1.76.0
Fixed versions: 1.76.0.
Conditions (all must be true for the bug to be hit):
- Uses rclone serve sftp with --auth-proxy (source: https://github.com/rclone/rclone/security/advisories/GHSA-66qv-66mg-9h74)
- The proxy handles public key and password logins differently (source: https://github.com/rclone/rclone/security/advisories/GHSA-66qv-66mg-9h74)
- The victim's cached key entry is still within its lifetime (source: https://github.com/rclone/rclone/security/advisories/GHSA-66qv-66mg-9h74)
- Attacker connects from the same client IP as the victim, same username; not a unix socket (source: https://github.com/rclone/rclone/security/advisories/GHSA-66qv-66mg-9h74)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134352 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134352 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-66qv-66mg-9h74
- https://www.vulncheck.com/advisories/rclone-1.51.0-before-1.76.0-authentication-bypass-via-serve-sftp-auth-proxy-cache
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-134352
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-134352"}.

Affected versions

cve.now Index

31Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach10/20Affects Go packages
  • Severity9.2/10CVSS 9.2
  • No patch0/5No signal

What would change the score

  • Would score about 81 if added to CISA KEV
  • Would score about 76 if CISA's SSVC rates exploitation active

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · rclone/rclone · Advisory GHSA-66qv-66mg-9h74
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134352
RecordNVD · CVE-2026-134352
Other links 1
Linkvulncheck.com · advisories/rclone-1.51.0-before-1.76.0-authentication-bypass-via-serve-sftp-auth-proxy-cache

Questions about CVE-2026-134352

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

With only the victim's public SSH key, an attacker can gain read and write access to the backend without the auth proxy being called. The proxy handles public key and password logins differently, and a victim's cached key entry can still be within its lifetime, which is refreshed on each access.

Source: github.com

Which versions are affected by CVE-2026-134352?

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

Source: cve.now feed data

Am I affected, and how do I check?

Versions from 1.51.0 before 1.76.0 using rclone serve sftp with --auth-proxy. Check the installed version with rclone version, and check whether the serve sftp command or its configuration includes --auth-proxy. The reported conditions also involve the same client IP and a non-unix-socket connection.

Source: github.com

How do I fix CVE-2026-134352?

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

Source: github.com

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