Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.2amended

RClone: Unauthenticated operations/fsinfo allows attacker-controlled backend instantiation and local command execution

CVE-2026-41179GHSA-jfwf-28xr-xw6q

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/ncw/rclone

    Affected
    >= 1.48.0
    Fixed in
    no fixed version recorded

  • Go github.com/rclone/rclone

    Affected
    >= 1.48.0, <= 1.73.4
    Fixed in
    1.73.5

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
9.2 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-41179: 8.58% estimated exploitation activity in the next 30 days; percentile 95.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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, bearertokencommand is executed during backend initialization, making single-request unauthenticated local command execution possible on reachable RC deployments without global HTTP authentication. Preconditions Preconditions for this vulnerability are: - The rclone remote control API must be enabled, either by the --rc flag or by running the rclone rcd server - The remote control API must be reachable by the attacker - by default rclone only serves the rc to localhost unless the --rc-addr flag is in use - The rc must have been deployed without global RC HTTP authentication - so not using --rc-user/--rc-pass/--rc-htpasswd/etc Details The root cause consists of the following pieces: 1.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-jfwf-28xr-xw6q

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GO-2026-5466

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41179

Advisory: RClone: Unauthenticated operations/fsinfo allows attacker-controlled backend instantiation and local command execution
IDs: CVE-2026-41179, GHSA-jfwf-28xr-xw6q
Record: https://patchnext.com/advisories/cve-2026-41179 (revision 3, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/rclone/rclone 1.73.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ncw/rclone: affected >= 1.48.0
- Go github.com/rclone/rclone: affected >= 1.48.0, <= 1.73.4; fixed in 1.73.5

## Suggested inspection (read-only)
- Go github.com/ncw/rclone: check the installed version with your package manager.
- Go github.com/rclone/rclone: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/ncw/rclone, github.com/rclone/rclone.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-5466 (OSV record GO-2026-5466 lists affected ranges: Go github.com/ncw/rclone >=1.48.0; Go github.com/rclone/rclone >=1.49.0 <1.73.5 (fixed))
- Verified: https://github.com/advisories/GHSA-jfwf-28xr-xw6q (GitHub-reviewed advisory GHSA-jfwf-28xr-xw6q lists affected ranges: Go github.com/rclone/rclone >=1.48.0 <=1.73.4)

Commands are suggestions: review each one before running it.

Loading voting…