External risk intelligence

Rclone SFTP Authentication Bypass via Serve Sftp Auth Proxy Cache.

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-134352

The vulnerability affects the Rclone SFTP server component when using the --auth-proxy configuration. While Rclone is a command-line tool often used for local data management or internal scripts, the 'serve sftp' command can be used to expose filesystems over the network. Since this is an optional service configuration rather than a default internet-facing service, public exposure is possible but not standard.

Authentication Bypass

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

An authentication bypass vulnerability has been identified in Rclone's SFTP serve functionality, specifically when utilizing the `--auth-proxy` option. This issue allows unauthorized read-write access by enabling attackers to reuse cached credentials under certain conditions, potentially exposing sensitive data.

  • An issue exists with Rclone's SFTP authentication proxy.
  • This bypass could allow unauthorized file access.
  • Assess Rclone SFTP proxy usage for exposure.

Attack Path

How an attacker could exploit the issue

An attacker who knows a victim's public key can bypass authentication to gain unauthorized read-write access to files. This is possible when the Rclone SFTP server is configured with an authentication proxy, and the attacker can submit the victim's public key as a password from the same client IP address. This allows the attacker to exploit a flaw in how the server generates cache keys, reusing cached entries to gain elevated access.

  • Requires knowledge of victim's public key.
  • Triggered by submitting public key as password.
  • Risk of unauthorized file access.

Live Threat

Current exploitation, exposure, and threat context

When the Rclone `serve sftp` functionality is configured with `--auth-proxy`, and an attacker possesses a victim's base64 encoded public key, they could potentially bypass authentication. This bypass occurs because the caching mechanism in the `generateCacheKey` function omits the authentication method, allowing the attacker to reuse a cached entry. If successful, this could grant read-write access to the virtual file system (VFS).

  • Rclone SFTP server VFS data.
  • Reusing a victim's cached public key.
  • Unauthorized read-write VFS access.

Operational Fix

Recommended remediation, mitigation, and detection steps

The rclone utility's SFTP server, when configured with `--auth-proxy`, contains a critical authentication bypass vulnerability. Attackers can exploit this by submitting a victim's public key as a password to reuse cached entries, granting read-write access. Affected teams must first identify all instances of rclone serving SFTP, determine network reachability and business criticality, and then locate the accountable owner for remediation planning.

  • Identify rclone SFTP deployments.
  • Verify network exposure and criticality.
  • Coordinate ownership for remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Rclone and why is it used?

Rclone is an open-source command-line program designed for managing and syncing files across various cloud storage providers and local filesystems. Beyond basic file transfers, it includes a 'serve' module that allows users to create custom SFTP servers, enabling them to expose local or cloud-hosted data over the network for remote access.

How does CVE-2026-134352 work?

This vulnerability is an authentication bypass, categorized as CWE-287 (Improper Authentication). It occurs because Rclone's SFTP 'serve' component fails to include the specific authentication method when generating a cache key. Because the system relies on an incomplete key, it may mistakenly accept a malicious request as valid, allowing an unauthorized user to successfully authenticate.

What triggers this authentication bypass?

An attacker needs the victim's base64 encoded public key and must send it as a password from the same client IP address that the victim is using. If the Rclone instance is not using the '--auth-proxy' configuration, this specific cache-reuse flaw is not triggered. Simply running Rclone for general file syncing without the SFTP server module does not expose the system to this issue.

How does Halo Surface Signal describe the risk?

Halo Surface Signal notes that while Rclone is typically used for internal scripts or local data, the 'serve sftp' command can intentionally make filesystems available over the network. Because this is an optional service configuration rather than a default feature, Halo classifies public exposure as 'Possible' rather than standard, meaning you should check if your Rclone instances are reachable from the internet.

Do I need to take action if I use Rclone?

First, audit your environment to find any instances where 'rclone serve sftp' is running with the '--auth-proxy' flag. If you find active instances, determine if they are exposed to the network or restricted to internal traffic. Once you identify these deployments, coordinate with the service owners to plan and apply the necessary software updates to move beyond the vulnerable version range.

References