CVE-2026-88013Network attack vector

Secret disclosure via cross-host redirect header forwarding

Published Sep 10, 2026 · Updated Sep 10, 2026

Sensitive-information exposure in Rclone rclone 1.49.0 through 1.75.0 allows remote attackers to obtain configured HTTP headers via redirects. The HTTP backend adds configured headers to requests but uses a client without a backend-specific redirect policy, causing nonstandard headers to follow cross-host redirects and protected headers to survive same-host HTTPS-to-HTTP redirects. Exploitation requires an HTTP remote with configured secret headers and a redirect controlled or influenced by the remote endpoint; successful exploitation discloses those secrets without altering data or interrupting service.

CVSS severity3.7
Low
EPSS probability0.18%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Sensitive-information exposure in Rclone rclone 1.49.0 through 1.75.0 allows remote attackers to obtain configured HTTP headers via redirects. The HTTP backend adds configured headers to requests but uses a client without a backend-specific redirect policy, causing nonstandard headers to follow cross-host redirects and protected headers to survive same-host HTTPS-to-HTTP redirects. Exploitation requires an HTTP remote with configured secret headers and a redirect controlled or influenced by the remote endpoint; successful exploitation discloses those secrets without altering data or interrupting service.

The record

CVE
CVE-2026-88013
Published
Sep 10, 2026
Updated
Sep 10, 2026
Vendor
Rclone
Product
rclone
Classifications
CWE-319, CWE-522, CWE-200
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 10, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 10, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 1.49.0, < 1.75.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Rclone · rcloneversion=>= 1.49.0, < 1.75.1

Published CVSS scores

3.7GitHubCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-319Cleartext Transmission of Sensitive Information
CWE-522Insufficiently Protected Credentials
CWE-200Exposure of Sensitive Information to an Unauthorized Actor

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo