CVE-2026-41179

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 6.8%, top 8% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 9%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
94.7%
KEV
Not listed

Published

April 23, 2026

Last Modified

June 30, 2026

Advisory Details (9)

Auto-updated Jul 12, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github, redhat.
github Patch Available🟡 PoC Available

Unauthenticated RC operations/fsinfo allows attacker-controlled backend instantiation and local command execution via WebDAV bearer_token_command · Advisory · rclone/rclone · GitHub

https://github.com/rclone/rclone/security/advisories/GHSA-jfwf-28xr-xw6q
redhat Patch Available

2460988 – (CVE-2026-41179) CVE-2026-41179 github.com/rclone/rclone: Rclone: Unauthenticated local command execution via exposed RC endpoint

https://bugzilla.redhat.com/show_bug.cgi?id=2460988
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-41179
generic

Documentation

https://rclone.org/changelog/#v1-73-5-2026-04-19
github_release Patch Available

rclone v1.73.5

Patch available: rclone/rclone v1.73.5

https://github.com/rclone/rclone/releases/tag/v1.73.5
github_commit

commit 2a9e952b38e0 (rclone/rclone)

Fix landed in rclone/rclone commit 2a9e952b38e0 — awaiting tagged release

https://github.com/rclone/rclone/commit/2a9e952b38e03a96bf40c9eb6e8e22199865ee3b
generic

rclone/fs/rc/cache.go at bf55d5e6d37fd86164a87782191f9e1ffcaafa82 · rclone/rclone · GitHub

https://github.com/rclone/rclone/blob/bf55d5e6d37fd86164a87782191f9e1ffcaafa82/fs/rc/cache.go
generic

rclone/fs/operations/rc.go at bf55d5e6d37fd86164a87782191f9e1ffcaafa82 · rclone/rclone · GitHub

https://github.com/rclone/rclone/blob/bf55d5e6d37fd86164a87782191f9e1ffcaafa82/fs/operations/rc.go
generic

rclone/backend/webdav/webdav.go at bf55d5e6d37fd86164a87782191f9e1ffcaafa82 · rclone/rclone · GitHub

https://github.com/rclone/rclone/blob/bf55d5e6d37fd86164a87782191f9e1ffcaafa82/backend/webdav/webdav.go

Vendor Advisories for CVE-2026-41179(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubunturclone (1.53.3-4ubuntu1.22.04.4) @ jammy2026-06-15ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/rclone/rclone—1.73.5—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 194 total refreshes for this CVE.

  1. 2026-07-13 22:30 UTCEPSS rescore
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-09 19:10 UTCEPSS rescore
  5. 2026-07-08 15:15 UTCEPSS rescore
  6. 2026-07-07 13:46 UTCEPSS rescore
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 16:27 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-01 15:06 UTCEPSS rescore
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-27 03:08 UTCEPSS rescore
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-24 14:05 UTCEPSS rescore
  19. 2026-06-23 21:33 UTCEPSS rescore
  20. 2026-06-22 14:25 UTCEPSS rescore
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-19 19:25 UTCEPSS rescore
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-18 17:52 UTCEPSS rescore
  25. 2026-06-17 17:53 UTCEPSS rescore
Show 75 more
  1. 2026-06-16 17:52 UTCEPSS rescore
  2. 2026-06-15 17:49 UTCEPSS rescore
  3. 2026-06-15 06:45 UTCEG score recompute
  4. 2026-06-15 06:45 UTCVendor advisory
  5. 2026-06-15 02:29 UTCEG score recompute
  6. 2026-06-15 02:29 UTCVendor advisory
  7. 2026-06-14 20:44 UTCEG score recompute
  8. 2026-06-14 20:44 UTCVendor advisory
  9. 2026-06-14 16:49 UTCEG score recompute
  10. 2026-06-14 16:49 UTCVendor advisory
  11. 2026-06-14 12:26 UTCEG score recompute
  12. 2026-06-14 12:26 UTCVendor advisory
  13. 2026-06-13 23:00 UTCEPSS rescore
  14. 2026-06-12 23:12 UTCEPSS rescore
  15. 2026-06-12 23:12 UTCEPSS rescore
  16. 2026-06-12 12:37 UTCEG score recompute
  17. 2026-06-12 12:37 UTCVendor advisory
  18. 2026-06-12 06:14 UTCEG score recompute
  19. 2026-06-12 06:14 UTCVendor advisory
  20. 2026-06-12 02:20 UTCEG score recompute
  21. 2026-06-12 02:20 UTCVendor advisory
  22. 2026-06-11 22:25 UTCEG score recompute
  23. 2026-06-11 22:25 UTCVendor advisory
  24. 2026-06-11 18:31 UTCEG score recompute
  25. 2026-06-11 18:31 UTCVendor advisory
  26. 2026-06-11 14:29 UTCEG score recompute
  27. 2026-06-11 14:29 UTCVendor advisory
  28. 2026-06-11 14:00 UTCEPSS rescore
  29. 2026-06-10 22:18 UTCEPSS rescore
  30. 2026-06-10 19:58 UTCEG score recompute
  31. 2026-06-10 16:02 UTCEG score recompute
  32. 2026-06-10 16:02 UTCVendor advisory
  33. 2026-06-10 13:22 UTCEPSS rescore
  34. 2026-06-10 13:22 UTCEPSS rescore
  35. 2026-06-10 12:07 UTCEG score recompute
  36. 2026-06-10 12:07 UTCVendor advisory
  37. 2026-06-10 08:13 UTCEG score recompute
  38. 2026-06-10 08:13 UTCVendor advisory
  39. 2026-06-10 03:54 UTCEG score recompute
  40. 2026-06-10 03:54 UTCVendor advisory
  41. 2026-06-09 23:59 UTCEG score recompute
  42. 2026-06-09 23:59 UTCVendor advisory
  43. 2026-06-09 17:37 UTCEG score recompute
  44. 2026-06-09 17:37 UTCVendor advisory
  45. 2026-06-09 13:42 UTCEG score recompute
  46. 2026-06-09 13:42 UTCVendor advisory
  47. 2026-06-09 09:47 UTCEG score recompute
  48. 2026-06-09 09:47 UTCVendor advisory
  49. 2026-06-09 03:31 UTCEG score recompute
  50. 2026-06-09 03:31 UTCVendor advisory
  51. 2026-06-08 14:17 UTCEPSS rescore
  52. 2026-06-08 14:17 UTCEPSS rescore
  53. 2026-06-08 12:07 UTCEG score recompute
  54. 2026-06-08 12:07 UTCVendor advisory
  55. 2026-06-08 08:04 UTCEG score recompute
  56. 2026-06-08 08:04 UTCVendor advisory
  57. 2026-06-08 04:10 UTCEG score recompute
  58. 2026-06-08 04:10 UTCVendor advisory
  59. 2026-06-08 00:14 UTCEG score recompute
  60. 2026-06-08 00:14 UTCVendor advisory
  61. 2026-06-07 20:14 UTCEG score recompute
  62. 2026-06-07 20:14 UTCVendor advisory
  63. 2026-06-07 16:19 UTCEG score recompute
  64. 2026-06-07 16:19 UTCVendor advisory
  65. 2026-06-07 15:25 UTCEPSS rescore
  66. 2026-06-07 15:25 UTCEPSS rescore
  67. 2026-06-07 12:24 UTCEG score recompute
  68. 2026-06-07 12:24 UTCVendor advisory
  69. 2026-06-07 08:30 UTCEG score recompute
  70. 2026-06-07 08:30 UTCVendor advisory
  71. 2026-06-07 04:35 UTCEG score recompute
  72. 2026-06-07 04:35 UTCEG score recompute
  73. 2026-06-06 23:30 UTCEG score recompute
  74. 2026-06-06 23:30 UTCVendor advisory
  75. 2026-06-06 18:30 UTCEG score recompute

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-41179.yaml
    First seen Jan 1, 2026

    RClone RC - Command Injection

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41179?
CVE-2026-41179 is a critical vulnerability published on April 23, 2026. 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…
When was CVE-2026-41179 disclosed?
CVE-2026-41179 was first published in the National Vulnerability Database on April 23, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41179 actively exploited?
CVE-2026-41179 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 94.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41179?
CVE-2026-41179 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-41179?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41179, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41179

Explore →

Is Your Infrastructure Affected by CVE-2026-41179?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs