CVE-2026-116188: rclone serve s3 1.75.0 before 1.75.2 Memory Limit Bypass via Multipart Overflow
rclone serve s3 versions 1.75.0 before 1.75.2 contain an integer overflow vulnerability in multipart reorder-memory accounting that bypasses the configured buffer limit. Attackers can open two concurrent current-part PUT requests declaring huge lengths to wrap the signed int64 counter and retain out-of-order parts in memory, exhausting the host.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/rcloneto a version that resolves this vulnerability.Fixed in 1.60.1+dfsg-2Fixed in 1.60.1+dfsg-4Fixed in 1.75.2-2 - Upgrade
Upgrade
bitnami/rcloneto a version that resolves this vulnerability.Fixed in 1.75.2 - Upgrade
Upgrade
alpine/rcloneto a version that resolves this vulnerability.Fixed in 1.75.2-r0 - Upgrade
Upgrade
debian/rcloneto a version that resolves this vulnerability.Fixed in 1.75.2-1 - Upgrade
Upgrade
rclone serve s3to a version that resolves this vulnerability.Fixed in 1.75.2
Event History
Frequently Asked Questions
What conditions are required to exploit this issue?
An attacker must be able to send multipart PUT requests to an exposed rclone serve s3 endpoint. The attack uses two concurrent current-part PUT requests with declared lengths large enough to overflow the signed 64-bit multipart reorder-memory counter.
What is the operational impact of a successful attack?
The overflow bypasses the configured buffer limit, allowing out-of-order multipart data to remain in memory. This can exhaust host memory and cause a denial of service.
Which deployments should be prioritized for remediation?
Prioritize rclone serve s3 deployments running versions 1.75.0 through before 1.75.2 that accept multipart PUT requests from untrusted or broadly accessible clients. The issue is remotely exploitable without authentication or user interaction according to the supplied vector.