Quick answers
- Is CVE-2026-116195 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116195 being exploited in the wild.
- How severe is CVE-2026-116195?
- Medium severity, with a CVSS score of 6.1, published 25 October 2026.
- Which products and versions are affected?
- Rclone before 1.75.2.
- Is there a fix for CVE-2026-116195?
- Yes: fixed in 1.75.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116195 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2026-116195?
- Check whether you run 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
- Fixed in: 1.75.2
Technical details
The vulnerability exists in the local backend's translateLink function, which trims the .rclonelink suffix from a path after validation, allowing a directory named "...rclonelink" to bypass containment checks and resolve to the parent of the destination root. The attack requires both --links and --metadata flags and affects versions before 1.75.2. An attacker with ability to create directories in the source tree can modify filesystem metadata (ownership, timestamps, extended attributes) outside the intended destination.
Affected products
- rclone rclone before 1.75.2
Timeline
- 2026-10-25: disclosed
- 2026-10-25: patched: version 1.75.2 released