dbcve.org
RcloneApplication

CVE-2026-41176

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

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. The RC endpoint `options/set` is exposed without `AuthRequired: true`, but it can mutate global runtime configuration, including the RC option block itself. Starting in version 1.45.0 and prior to version 1.73.5, an unauthenticated attacker can set `rc.NoAuth=true`, which disables the authorization gate for many RC methods registered with `AuthRequired: true` on reachable RC servers that are started without global HTTP authentication. This can lead to unauthorized access to sensitive administrative functionality, including configuration and operational RC methods. 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

Rclone versions 1.45.0 through 1.73.4 expose the RC endpoint `options/set` without authentication, allowing unauthenticated attackers to modify global runtime configuration including setting `rc.NoAuth=true`, which disables authorization for all RC methods. This affects RC servers started without global HTTP authentication, enabling full administrative access.

MitigationUpgrade Rclone to version 1.73.5 or later. Additionally, ensure RC servers are started with global HTTP authentication enabled and restrict network access to RC endpoints.

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.45, < 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 rclone installed version
    Run 'rclone version' and examine the version number in the output
    Affected if The version is 1.45 or higher but lower than 1.73.5
  2. Verify RC endpoint is exposed
    Check if the rclone RC service is running by querying localhost on the RC port (default 5572) with: curl http://localhost:5572/rc/
    Affected if The RC endpoint responds, indicating the RC service is active and accessible
  3. Determine if RC was started without global HTTP authentication
    Review how the rclone RC process was started; check for the absence of --rc-user and --rc-pass flags or equivalent configuration
    Affected if The RC server was started without --rc-user/--rc-pass or without setting rc.user/rc.pass in the config, meaning no global HTTP authentication is enforced
  4. Check current rc.NoAuth configuration state
    Query the RC options endpoint: curl http://localhost:5572/options/get -d '{}' and inspect the response for the 'rc' block, specifically the 'NoAuth' field
    Affected if The rc.NoAuth field is set to true, indicating authentication has been disabled

A user is affected if they are running rclone version 1.45 to 1.73.5, have the RC endpoint exposed, started RC without global HTTP authentication (--rc-user/--rc-pass), and rc.NoAuth is currently set to true or the endpoint is accessible without credentials.

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
Interim mitigation

Upgrade Rclone to version 1.73.5 or later. Additionally, ensure RC servers are started with global HTTP authentication enabled and restrict network access to RC endpoints.

Recommended fix High confidence

rclone >= 1.73.5

  1. Check current rclone version by running `rclone version`
  2. Download rclone version 1.73.5 or later from the official releases at https://downloads.rclone.org/rclone-current-linux-amd64.zip (or appropriate platform)
  3. Extract and replace the existing rclone binary with the new version
  4. Verify the upgrade was successful by running `rclone version` and confirming it shows 1.73.5 or later
  5. If using rclone as a service, restart the rclone RC server to apply the new binary
Caveat Review the release notes between your current version and 1.73.5 for any breaking changes specific to your use case

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41176 — 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-41176 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