Skip to main content
Menu
CVEs

Rclone symlink escape writes xattrs outside destination root

Only affects rclone 1.59.0 up to 1.76.0 when run with --links and --metadata on the local backend. Fixed in 1.76.0.

CVE-2026-134354Published November 21, 2026, updated

5.1MediumCNA
Exploited
No known exploitation
Fix
Fixed in 1.76.0
Who is exposed
Specific setups only

Summary

Written by a model

rclone from 1.59.0 before 1.76.0 contains a confinement escape in the local backend's setXattr function that lets attackers write user.* extended attributes outside the destination root via a planted symlink. Attackers who plant a symlink to an outside directory with a pre-existing child can use --links --metadata operations to set attacker-chosen user.* xattrs on files outside the destination.

Who should check

Teams running rclone 1.59.0 through 1.75.x with --links and --metadata on local destinations that other parties can write to.

Not fixed by: Upgrading to v1.75.1 (the CVE-2026-88016 fix) does not fix this.

“rclone local --links --metadata writes attacker-chosen user.* xattrs outside the destination root”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    rclone 1.59.0 up to but not including 1.76.0 Local backend run with --links (symlink translation) and --metadata A planted symlink in the destination pointing outside the root A pre-existing child entry exists under the symlink's outside target
  2. Upgrade to a fixed version: 1.76.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134354 (rclone 1.59.0 before 1.76.0 Symlink Escape via Extended Attribute Metadata Write), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134354 (entry last updated 2026-11-21):
Affected:
- Go package github.com/rclone/rclone: from 1.59.0, fixed in 1.76.0
Fixed versions: 1.76.0.
Conditions (all must be true for the bug to be hit):
- rclone 1.59.0 up to but not including 1.76.0 (source: https://www.vulncheck.com/advisories/rclone-1.59.0-before-1.76.0-symlink-escape-via-extended-attribute-metadata-write)
- Local backend run with --links (symlink translation) and --metadata (source: https://github.com/rclone/rclone/security/advisories/GHSA-r5wv-vqqh-2r9c)
- A planted symlink in the destination pointing outside the root (source: https://github.com/rclone/rclone/security/advisories/GHSA-r5wv-vqqh-2r9c)
- A pre-existing child entry exists under the symlink's outside target (source: https://github.com/rclone/rclone/security/advisories/GHSA-r5wv-vqqh-2r9c)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: local access, no login, no user action.
CISA KEV: CVE-2026-134354 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134354 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/rclone/rclone/security/advisories/GHSA-r5wv-vqqh-2r9c
- https://www.vulncheck.com/advisories/rclone-1.59.0-before-1.76.0-symlink-escape-via-extended-attribute-metadata-write
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134354
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134354"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach10/20Affects Go packages
  • Severity5.1/10CVSS 5.1
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 30 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · rclone/rclone · Advisory GHSA-r5wv-vqqh-2r9c
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134354
RecordNVD · CVE-2026-134354
Other links 1
Linkvulncheck.com · advisories/rclone-1.59.0-before-1.76.0-symlink-escape-via-extended-attribute-metadata-write

Questions about CVE-2026-134354

Is CVE-2026-134354 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A planted symlink in the destination can redirect a write outside the destination root, letting an attacker set chosen user.* extended attributes on files or directories there. Content, mode, owner and times stay confined to the destination.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134354?

github.com/rclone/rclone (Go): from 1.59.0 before 1.76.0.

Source: cve.now feed data

Am I affected, and how do I check?

rclone 1.59.0 up to but not including 1.76.0 is affected, but only when the local backend is run with both --links (symlink translation) and --metadata. The version can be checked with rclone version, and the flags are checked in the command or configuration used to run rclone.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134354?

Upgrade to rclone 1.76.0 or later, which contains the fix.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.