Answer in brief
CVE-2026-88013 records a Low severity (CVSS 3.7) vulnerability in rclone: http backend forwards custom/auth headers to a different host on redirect. 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 3.7. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:rclone:rclone:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| rclone/rclonegeneric | >=1.49.0 <1.75.1 | 1.75.1 |
| github.com/rclone/rclonego | >=1.49.0,<=1.75.0 | 1.75.1 |
| github.com/rclone/rclonego | >=1.49.0 <1.75.1 | 1.75.1 |
Published upstream
Sep 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 23, 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.49.0 until 1.75.1, the HTTP backend attaches headers configured through --http-headers or headers= to requests in backend/http/http.go, while its fshttp.NewClient client follows redirects without a backend-specific http.Client.CheckRedirect policy. A configured remote that redirects to another host can therefore cause custom secrets such as X-Api-Key to be resent to that untrusted destination, and a same-host HTTPS-to-HTTP redirect can expose Authorization or Cookie headers in cleartext. Listing, stat, download, mount, and serve operations can trigger the leak during normal use. This issue is fixed in version 1.75.1.
Quoted source text, attributed separately from HOL analysis.