Is CVE-2026-54572 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-54572 being exploited in the wild.

How severe is CVE-2026-54572?

High severity, with a CVSS score of 7.5, published 14 July 2026.

Which products and versions are affected?

github.com/rclone/rclone (Go) <= 1.74.3, SEMVER:introduced=0,fixed=1.74.4; Rclone < 1.74.4, <= 1.74.3.

Is there a fix for CVE-2026-54572?

Yes. github.com/rclone/rclone (Go): upgrade to 1.74.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-54572 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-54572?

Check whether you run github.com/rclone/rclone (Go) or Rclone at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-54572: Rclone improper link resolution in local destination sync

Q: Is there a fix for CVE-2026-54572?

Yes. github.com/rclone/rclone (Go): upgrade to 1.74.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-54572 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-54572?

Check whether you run github.com/rclone/rclone (Go) or Rclone at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-54572 · Severity: high · CVSS 7.5 · Published 2026-07-14

rclone, a popular command-line tool for managing files on cloud storage, is vulnerable to a security flaw when using the '--links' feature. An attacker who controls a remote storage location can trick rclone into creating malicious shortcuts (symlinks) on a user's computer. This allows the attacker to overwrite sensitive system files, potentially leading to full unauthorized access or control over the victim's machine.

Technologies: github.com/rclone/rclone (Go), Rclone. Vendors: Go, Rclone.

Quick answers

Is CVE-2026-54572 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-54572 being exploited in the wild.
How severe is CVE-2026-54572?: High severity, with a CVSS score of 7.5, published 14 July 2026.
Which products and versions are affected?: github.com/rclone/rclone (Go) <= 1.74.3, SEMVER:introduced=0,fixed=1.74.4; Rclone < 1.74.4, <= 1.74.3.
Is there a fix for CVE-2026-54572?: Yes. github.com/rclone/rclone (Go): upgrade to 1.74.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54572 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-54572?: Check whether you run github.com/rclone/rclone (Go) or Rclone at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/rclone/rclone (Go): upgrade to 1.74.4 or later
```
go get github.com/rclone/rclone@v1.74.4
```

Technical details

A vulnerability exists in rclone's local backend (backend/local/local.go) within the Object.Update() function. When the -l/--links flag is used, rclone serializes symlinks as .rclonelink files but fails to validate the link target when recreating them at the destination. An attacker controlling a remote source can provide a symlink target containing absolute paths or directory traversal sequences (../). Because rclone processes these objects in a specific order and follows existing symlinks during subsequent file writes without using O_NOFOLLOW, it can be coerced into writing files outside the intended destination directory. This can result in arbitrary file overwrite and remote code execution if sensitive files like ~/.ssh/authorized_keys are targeted. The issue is fixed in version 1.74.4.

Affected products

rclone rclone <= 1.74.3

Identifiers

CVE-2026-54572
GHSA-cf44-9pgv-m4xc
GO-2026-6191

Timeline

2026-07-08: disclosed
2026-07-14: advisory: NVD publication date
2026-08-05: patched: GitHub Advisory published/updated date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.