Answer in brief
CVE-2026-88045 records a High severity (CVSS 7.5) vulnerability in rclone: S3 multipart declared-length memory exhaustion. The current sources do not mark it as known exploited. The current feed maps rclone/rclone (generic), github.com/rclone/rclone (go), github.com/rclone/rclone (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps rclone/rclone (generic), github.com/rclone/rclone (go), github.com/rclone/rclone (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| rclone/rclonegeneric | >= 1.75.0, < 1.75.1 | Not reported |
| github.com/rclone/rclonego | =1.75.0 | 1.75.1 |
| github.com/rclone/rclonego | >=1.75.0 <1.75.1 | 1.75.1 |
Published upstream
Sep 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 10, 2026
rclone is a command-line program to sync files and directories to and from different cloud storage providers. From 1.75.0 until 1.75.1, the serve S3 streamed multipart path in cmd/serve/s3/multipart.go passes attacker-controlled contentLength to multipart.NewRW().Reserve before reading request-body bytes. waitForTurn admits the current part and one oversized part when the buffer is empty despite --multipart-streaming-buffer-limit, and lib/pool allocates 1 MiB pages according to Content-Length or X-Amz-Decoded-Content-Length. A network client can retain or multiply these reservations without sending the declared body, exhausting process or host memory or permanently blocking request handlers. Anonymous S3 deployments require no credentials, while deployments using auth_key require an accepted S3 key. This issue is fixed in version 1.75.1.
Quoted source text, attributed separately from HOL analysis.