/

CVE-2026-88044

Severity:

CRITICAL RISK

(9.1)

Improper Authorization (CWE-863) in rclone RC Servers

CVE-2026-88044

Awaiting Analysis

Vulnerability type

Category:

Improper Authorization

CWE:

CWE-863

Impact:

Unauthorized resource access and potential data exposure

Severity:

CRITICAL RISK

(9.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A request-scoping authorization flaw in rclone's remote-control (RC) serving interface can cause FTP and S3 servers to ignore request-specific authentication proxy settings. Under affected configurations, a request may receive access to a fixed filesystem or RC backend without the intended authorization boundary being applied.

Affected context

The issue occurs in rclone versions that expose FTP or S3 servers through the serve/start RC interface and configure authentication proxy settings per server request. It is relevant when the process-global proxy authentication setting is empty while a request-local setting is supplied. Dedicated command-line servers that configure the global option are not generally affected by this specific behavior.

Exploit preconditions

  • Attack surface: The rclone remote-control interface used to create or start FTP or S3 servers
  • Required access: Access sufficient to invoke the relevant RC server configuration operation, together with a reachable resulting service
  • Trigger point: Construction of an FTP or S3 server using request-local proxyOpt.AuthProxy settings
  • Why exploitation is possible: The constructors consult process-global authentication state instead of the request-specific value, causing the intended authorization proxy to be skipped when the global setting is empty

Why this happens

The vulnerability results from confusing process-global configuration with request-local security state. Authentication and authorization decisions are made using a global proxy option rather than the per-server settings supplied for the current request. This maps to CWE-863: Incorrect Authorization, because access-control behavior can differ from the policy intended for the specific server or request.

Potential impact

  • An attacker may access a fixed FTP filesystem with unintended anonymous credentials
  • An attacker could reach an RC-backed S3 service without the intended authentication proxy
  • Sensitive files or object data may be disclosed or modified
  • Backend isolation and tenant boundaries could be bypassed
  • Downstream systems may trust services that were created without their configured authorization layer

General mitigation guidance

Mitigation generally focuses on preserving security-relevant configuration at the narrowest applicable scope and failing closed when authorization state is missing or inconsistent.

Common defensive patterns include:

  • Use request-local authentication and authorization settings when constructing each server
  • Avoid relying on mutable process-global security configuration for per-request decisions
  • Reject server creation when required authorization settings are absent or ambiguous
  • Prefer authenticated, explicitly scoped backends over anonymous or fixed fallback filesystems
  • Apply least privilege to filesystem paths, storage credentials, and RC operations
  • Restrict access to the RC interface through network policy, identity controls, and administrative boundaries

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis that identifies security decisions reading global configuration instead of request-scoped state
  • Code review checks for fallback to anonymous identities or fixed backends when authentication configuration is empty
  • Tests that create multiple servers with different per-request authorization settings and verify isolation
  • Policy enforcement requiring authentication for RC interfaces and rejecting unscoped backend creation
  • Runtime monitoring for unexpected anonymous FTP sessions, unplanned RC filesystem exposure, or server instances whose effective authorization differs from their requested configuration

Sources

SourceLink
github.comgithub.com/rclone/rclone/commit/739403963abf6f58003c2becd5f7c4ad0d644153
github.comgithub.com/rclone/rclone/releases/tag/v1.75.1
github.comgithub.com/rclone/rclone/security/advisories/GHSA-p569-5gjg-9cmj

Frequently asked

questions

It may be exploitable over a network when an attacker can reach the RC interface or otherwise obtain the ability to create or configure the affected FTP or S3 server.

Authentication requirements depend on how the RC interface is exposed. The key prerequisite is sufficient access to invoke the server-management operation, combined with access to the resulting service.

Ensure every server construction path uses the authorization configuration belonging to the current request, rejects missing security settings, and does not silently fall back to anonymous or fixed backends.

Keep authorization state request-scoped, test isolation between differently configured server instances, restrict RC exposure, and enforce least-privilege policies for all exposed filesystems and storage backends.

Find out what's already
exploitable in your codebase.