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 VendorProductAffected 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
Fix within
Internet-facing 14 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically (estimated)
  • Gives an attacker partial control (estimated)
Severity
3.7 Low
Timeline
Published11 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
Track software like this
Free during beta