dbcve.org
RcloneApplication

CVE-2026-41179

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-23
Fix available
A fix is available. Upgrade to 1.73.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Rclone is a command-line program to sync files and directories to and from different cloud storage providers. Starting in version 1.48.0 and prior to version 1.73.5, the RC endpoint `operations/fsinfo` is exposed without `AuthRequired: true` and accepts attacker-controlled `fs` input. Because `rc.GetFs(...)` supports inline backend definitions, an unauthenticated attacker can instantiate an attacker-controlled backend on demand. For the WebDAV backend, `bearer_token_command` is executed during backend initialization, making single-request unauthenticated local command execution possible on reachable RC deployments without global HTTP authentication. Version 1.73.5 patches the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Rclone RC (remote control) endpoint `/operations/fsinfo` lacks authentication enforcement and accepts attacker-controlled `fs` input. Through inline backend definitions in `rc.GetFs(...)`, an unauthenticated attacker can instantiate a WebDAV backend with a `bearer_token_command` that executes during backend initialization, achieving single-request local command execution on reachable RC deployments.

MitigationUpgrade to Rclone version 1.73.5 or later to patch the vulnerability. If immediate upgrading is not feasible, disable the RC interface or enforce network-level access controls to prevent unauthorized access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RcloneApplication
Affected:>= 1.48.0, < 1.73.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed rclone version
    Run `rclone version` or `rclone --version` to retrieve the version number
    Affected if The version is >= 1.48.0 and < 1.73.5
  2. Verify RC interface is running
    Check if the rclone RC service is active, typically on port 5572. Use `rclone rc` to start it or check running processes with `ps aux | grep rclone`. Look for RC-specific flags like `--rc`, `--rc-addr`, or `--rc-web-gui` in the process list or systemd service
    Affected if The RC interface is enabled and listening on a network interface accessible to attackers (e.g., 0.0.0.0 or external IP)
  3. Confirm RC authentication is disabled or missing
    Inspect the rclone configuration or startup flags for `--rc-user` and `--rc-pass`. If these are absent, authentication is not enforced. Check config files or systemd unit files for RC-related settings
    Affected if No RC authentication credentials are configured, meaning the RC endpoints are unauthenticated
  4. Test access to the vulnerable endpoint
    Send an HTTP GET request to `http://<rc-address>:5572/operations/fsinfo?fs=/` or with a WebDAV inline backend parameter. Example: `curl 'http://localhost:5572/operations/fsinfo?fs=webdav://user:pass@host/'`. A successful response indicates the endpoint is reachable without authentication
    Affected if The endpoint responds successfully without requiring authentication credentials

You are affected if rclone version is between 1.48.0 and 1.73.5, the RC interface is enabled and network-accessible, and no RC authentication is configured, allowing unauthenticated access to the operations/fsinfo endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.73.5 or later
Fixed in 1.73.5
Vendor patch github.com →
Interim mitigation

Upgrade to Rclone version 1.73.5 or later to patch the vulnerability. If immediate upgrading is not feasible, disable the RC interface or enforce network-level access controls to prevent unauthorized access.

Recommended fix High confidence

1.73.5

  1. Check the current rclone version by running: rclone version
  2. Download rclone version 1.73.5 (or latest stable version) from the official rclone releases page: https://downloads.rclone.org/rclone-current-linux-amd64.zip (adjust for your OS/architecture)
  3. Extract the downloaded archive
  4. Replace the existing rclone binary with the new version (typically in /usr/bin/rclone or /usr/local/bin/rclone)
  5. Verify the upgrade was successful by running: rclone version
  6. If you have an active rclone RC (remote control) service running, restart it to apply the patched binary
  7. Confirm the RC endpoint now requires authentication or the vulnerable endpoint is properly secured
Caveat Review the rclone v1.73.5 release notes for any breaking changes between your current version and 1.73.5, particularly around RC authentication defaults

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rclone Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41179 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41179 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data