Live › vulnerability › CVE-2026-116187
Go to dashboardRclone's serve s3 --auth-proxy mode does not check that a multipart upload ID belongs to the requesting tenant. An authenticated tenant who learns another tenant's bucket, object and upload ID can add parts, complete or abort that upload, and read upload and object metadata.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-25 14:41 UTC. All times on this page are UTC.
Teams that run rclone's S3 server with the --auth-proxy option so several tenants share one endpoint. A single-user rclone install or a plain serve s3 without an auth proxy is not described as affected by the sources.
No product ranges from the sources yet.
rclone version and confirm the installed version is below v1.75.2serve s3 and --auth-proxy (for example in the process list or service unit)v1.75.2 or laterserve s3 --auth-proxy to tenants you do not fully trustEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Rclone from v1.68.0 before v1.75.2 contains an authorization bypass vulnerability in serve s3 --auth-proxy that allows authenticated tenants to manipulate other tenants' multipart uploads by referencing their upload IDs. Attackers who learn a victim's bucket, object, and upload ID can inject parts, complete, or abort in-flight uploads and view upload and object metadata across tenants.
This page as .md · .json · in your agent: get_signal("CVE-2026-116187")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.