- Veröffentlicht
- 10.09.2026 17:39
- Zuletzt geändert
- 19.11.2026
- EPSS (30 Tage)
- 0.2 %
- CVSS-Vektor
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Beschreibung
Originaltext der Quelle, nicht übersetzt.
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.
Status beim Hersteller
Red Hat stuft seine Produktlinien ein: 2 betroffen.
Cryostat 4
BetroffenFix zurückgestellt
cryostat/cryostat-storage-rhel9
Red Hat Advanced Cluster Management for Kubernetes 2
BetroffenFix zurückgestellt
rhacm2/volsync-rhel9
Weitere betroffene Pakete (24)
Bitnamirclone1.49.0 → 1.75.1BIT-rclone-2026-88013
CVErclone/rclonekein Fix bekanntCVE-2026-88013
Debian:12rclonekein Fix bekanntDEBIAN-CVE-2026-88013
Debian:13rclonekein Fix bekanntDEBIAN-CVE-2026-88013
Debian:14rclone1.75.2-1DEBIAN-CVE-2026-88013
Docker Hardened Images:Alpine:3.24telegrafkein Fix bekanntDHI-xzid-334r-aly4-opbl
Docker Hardened Images:Alpine:3.24telegraf-devkein Fix bekanntDHI-xzid-334r-aly4-opbl
Docker Hardened Images:Alpine:3.24telegraf-fipskein Fix bekanntDHI-xzid-334r-aly4-opbl
Docker Hardened Images:Alpine:3.24telegraf-fips-devkein Fix bekanntDHI-xzid-334r-aly4-opbl
Docker Hardened Images:Debian:13arangodbkein Fix bekanntDHI-xzid-334r-aly4-opbl
Gogithub.com/rclone/rclone1.49.0 → 1.75.1GHSA-486v-q2wf-fp2r
Gogithub.com/rclone/rclone1.49.0 → 1.75.1GO-2026-6463
NVDrclone:rclone1.49.0 → 1.75.1CVE-2026-88013
SUSE:Linux Enterprise Server 16.0govulncheck-vulndb0.0.20260916T180043-160000.1.1SUSE-SU-2026:23855-1
SUSE:Linux Enterprise Server 16.0govulncheck-vulndb0.0.20260916T180043-160000.1.1SUSE-SU-2026:23863-1
SUSE:Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20260916T180043-160000.1.1SUSE-SU-2026:23855-1
SUSE:Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20260916T180043-160000.1.1SUSE-SU-2026:23863-1
Ubuntu:18.04:LTSrclonekein Fix bekanntUBUNTU-CVE-2026-88013
Ubuntu:26.10rclonekein Fix bekanntUBUNTU-CVE-2026-88013
Ubuntu:Pro:20.04:LTSrclonekein Fix bekanntUBUNTU-CVE-2026-88013
Ubuntu:Pro:22.04:LTSrclonekein Fix bekanntUBUNTU-CVE-2026-88013
Ubuntu:Pro:24.04:LTSrclonekein Fix bekanntUBUNTU-CVE-2026-88013
Ubuntu:Pro:26.04:LTSrclonekein Fix bekanntUBUNTU-CVE-2026-88013
openSUSE:Leap 16.0govulncheck-vulndb0.0.20260916T180043-160000.1.1openSUSE-SU-2026:21897-1
Empfohlene Prüfung
- Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
- Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
- Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.
Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.
Referenzen
- github.com/rclone/rclone/security/advisories/GHSA-486v-q2wf-fp2r
- github.com/rclone/rclone/commit/22859b7e696cea3c563c6ba04c6b7f91f74456b4
- github.com/rclone/rclone/commit/79fbc0842f74e02cb84f0e3e7261d169983c8831
- github.com/rclone/rclone/commit/925fb4fb21eb25e75cd1b64fdd17ded857784bfc
- github.com/rclone/rclone/releases/tag/v1.75.1
- nvd.nist.gov/vuln/detail/CVE-2026-88013
- security-tracker.debian.org/tracker/CVE-2026-88013
- scout.docker.com/v/DHI-xzid-334r-aly4-opbl
- security.alpinelinux.org/vuln/CVE-2026-88013
- alas.aws.amazon.com/AL2023/ALAS-2026-3129.html
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- cve.mitre.org/cgi-bin/cvename.cgi
- github.com/advisories/GHSA-486v-q2wf-fp2r
- pkg.go.dev/vuln/GO-2026-6463
- access.redhat.com/security/cve/CVE-2026-88013
- www.cve.org/CVERecord
- ubuntu.com/security/CVE-2026-88013
- people.ubuntu.com/~ubuntu-security/cve/CVE-2026-88013
- github.com/rclone/rclone
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-88013.json
- bugzilla.redhat.com/show_bug.cgi