CVE-2026-134351 in Rcloneinfo

Summary

by MITRE • 11/21/2026

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.

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The identified security flaw resides within the authentication proxy mechanism of Rclone versions prior to 1.76.0, specifically affecting the Proxy.Call function which handles credential validation for remote storage services. This vulnerability is classified as an improper authentication issue where the system fails to properly validate user credentials against current authorization states before granting access. The core technical deficiency lies in the caching strategy employed by the proxy layer. When a user successfully authenticates via protocols such as SFTP, FTP, HTTP, or WebDAV, the resulting positive authentication response is cached for reuse. However, this cache entry lacks any mechanism to revalidate its status against the central identity provider or authorization service during its validity period. Consequently, if an administrator revokes a user's access rights after they have already authenticated and established a session, the system continues to serve the stale cached approval rather than checking the updated permission state.

This architectural oversight allows revoked users to maintain active connections indefinitely within the cache window, which is set to five minutes in this implementation. During this timeframe, even though the user's account has been explicitly disabled or their permissions removed at the source of truth, any subsequent connection attempts using their original credentials are met with a cached positive response from the proxy layer. This effectively bypasses the intended access control policies, granting unauthorized individuals continued read and write capabilities to sensitive data stored on remote backends such as cloud storage buckets, network shares, or object stores. The impact is particularly severe in environments where rapid user offboarding or permission changes are critical for compliance and security hygiene, as it creates a window of opportunity for data exfiltration or malicious modification that goes undetected by standard access control logs which may only record the initial successful login rather than subsequent unauthorized actions enabled by stale tokens.

From an industry standards perspective, this vulnerability aligns with CWE-287 Improper Authentication and CWE-613 Insufficient Session Expiration. The failure to revalidate session state against a central authority is also indicative of weaknesses often associated with ATT&CK technique T1078 Valid Accounts, where attackers leverage legitimate credentials that have not been properly invalidated by administrative actions. In enterprise deployments utilizing Rclone as part of larger data pipeline architectures, this flaw undermines the principle of least privilege and can lead to significant regulatory non-compliance depending on the sensitivity of the stored data. The persistence of access despite revocation suggests a lack of real-time synchronization between identity management systems and application-level authentication proxies, highlighting a common pitfall in distributed system design where performance optimization through caching inadvertently compromises security posture by introducing stale state dependencies.

To mitigate this risk, organizations must immediately upgrade Rclone to version 1.76.0 or later, which addresses the improper revalidation logic within the Proxy.Call function. In scenarios where an immediate upgrade is not feasible due to operational constraints, administrators should implement network-level controls such as firewall rules that restrict access to affected services during maintenance windows when user permissions are being updated. Additionally, reducing session timeouts and cache durations can minimize the window of exposure, although this may impact performance for legitimate high-throughput operations. It is also advisable to audit recent authentication logs for any anomalous activity from recently revoked accounts within the last five minutes prior to patching. Long-term architectural improvements should include implementing short-lived tokens with mandatory refresh cycles that require re-authentication against a central identity provider, thereby ensuring that access decisions are always based on current authorization states rather than cached historical approvals.

Responsible

VulnCheck

Reservation

11/21/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!