Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.7
Docker Telegraf images can unintentionally send secret headers
published 10 days ago
Summary
The Telegraf Docker images that include rclone may forward custom authentication headers to unexpected locations when a cloud storage request is redirected. This can expose API keys or cookies to untrusted sites or over an unsecured connection. Update rclone to version 1.75.1 or later in those images to stop the header leakage.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Docker Hardened Images:Alpine:3.24 | docker hardened images | telegraf-dev | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | telegraf-fips-dev | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | telegraf-fips | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | telegraf | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | arangodb | All versions |
Original advisory text
rclone is a command-line program to sync files and directories to and from different cloud storage providers. From…
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.
References
- https://scout.docker.com/v/DHI-xzid-334r-aly4-opbl Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-88013 Vendor Advisory
- https://github.com/rclone/rclone/security/advisories/GHSA-486v-q2wf-fp2r Vendor Advisory
- https://github.com/rclone/rclone/commit/925fb4fb21eb25e75cd1b64fdd17ded857784bfc Patch
- https://github.com/rclone/rclone/commit/79fbc0842f74e02cb84f0e3e7261d169983c8831 Patch
- https://github.com/rclone/rclone/commit/22859b7e696cea3c563c6ba04c6b7f91f74456b4 Patch
- https://github.com/rclone/rclone/releases/tag/v1.75.1 URL
- https://security.alpinelinux.org/vuln/CVE-2026-88013 Vendor Advisory
- https://alas.aws.amazon.com/AL2023/ALAS-2026-3129.html Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-88046 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-88044 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-88018 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-88017 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-88016 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-88015 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-88014 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-88013 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-79783 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-79782 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-79781 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-79780 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-79779 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-79778 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-79777 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-79776 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-79775 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-78662 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-71313 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-59732 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-56855 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-56854 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-46603 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-42505 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-39822 Vendor Advisory
- https://security-tracker.debian.org/tracker/CVE-2026-88013 Vendor Advisory
- https://github.com/advisories/GHSA-486v-q2wf-fp2r Vendor Advisory
- https://pkg.go.dev/vuln/GO-2026-6463 Vendor Advisory
- https://access.redhat.com/security/cve/CVE-2026-88013 Vendor Advisory
- https://www.cve.org/CVERecord?id=CVE-2026-88013 Patch
- https://ubuntu.com/security/CVE-2026-88013 Vendor Advisory
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-88013 Vendor Advisory
Internet-facing
14 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically (estimated)
- Gives an attacker partial control (estimated)
Timeline
Published11 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
DHI-xzid-334r-aly4-opbl · OSV
Track software like this
Free during beta