Quick answers
- Is CVE-2026-116187 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116187 being exploited in the wild.
- How severe is CVE-2026-116187?
- Medium severity, with a CVSS score of 5, published 25 October 2026.
- Which products and versions are affected?
- Rclone v1.68.0 to v1.75.1.
- Is there a fix for CVE-2026-116187?
- Yes: fixed in v1.75.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116187 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116187?
- 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: v1.75.2
Technical details
The vulnerability is an authorization bypass in multipart upload operations (UploadPart, CompleteMultipartUpload, AbortMultipartUpload) that are resolved by upload ID alone without re-checking the authenticated tenant context. While ordinary S3 object operations properly scope to the caller's VFS via per-request context, multipart operations use a process-global map with no tenant dimension. An authenticated attacker with knowledge of a victim's bucket, object name, and upload ID—obtainable via ListMultipartUploads if they own a same-named bucket—can manipulate in-flight uploads; the victim's object key is fixed by the initiator so this is not arbitrary cross-tenant write of at-rest content, but upload and custom object metadata are leaked.
Affected products
- Rclone Rclone v1.68.0 to v1.75.1
Timeline
- 2026-10-09: disclosed
- 2026-10-25: advisory