Categories
CVE-2026-41179 critical CVSS 9.8

OS Command Injection in github.com/rclone/rclone (CVE-2026-41179)

Summary

OS command injection in github.com/rclone/rclone (CVE-2026-41179). Successful exploitation can lead to full system takeover. Exploitable via bearer_token_command. Mitigation: upgrade to 1.73.5 or later.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-41179 has been found in github.com/rclone/rclone.
Attackers can target a specific entry point like bearer_token_command over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade github.com/rclone/rclone to 1.73.5 or later.
If unsure, ask your IT team or search "github.com/rclone/rclone CVE-2026-41179" on the vendor's site.

CVE-2026-41179 (github.com/rclone/rclone) — CWE-78 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: bearer_token_command / master / bf55d5e6d37fd86164a87782191f9e1ffcaafa82
Patched: 1.73.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

OS command injection (CWE-78) exists in github.com/rclone/rclone. Attackers reach the vulnerable code path via bearer_token_command without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/rclone/rclone. Attack surface: bearer_token_command / master / bf55d5e6d37fd86164a87782191f9e1ffcaafa82.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.73.5.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/rclone/rclone' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'github.com/rclone/rclone' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/rclone/rclone を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade github.com/rclone/rclone to 1.73.5

    ステージング環境で 1.73.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/rclone/rclone
[{"type":"SEMVER","events":[{"introduced":"1.49.0"},{"fixed":"1.73.5"}]}]
Bitnami rclone
[{"type":"SEMVER","events":[{"introduced":"1.48.0"},{"fixed":"1.73.5"}]}]
Go github.com/ncw/rclone
[{"type":"SEMVER","events":[{"introduced":"1.48.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details