BIT-rclone-2026-88018
See a problem?- Import Source
- https://github.com/bitnami/vulndb/tree/main/data/rclone/BIT-rclone-2026-88018.json
- JSON Data
- https://api.osv.dev/v1/vulns/BIT-rclone-2026-88018
- Aliases
- Published
- 2026-09-15T08:49:34Z
- Modified
- 2026-09-15T09:25:55Z
- Summary
- rclone serve s3: --auth-proxy without --auth-key authenticates nobody - full SigV4 signature bypass
- Details
-
rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.75.1, rclone serve s3 configured with --auth-proxy but without --auth-key allows authPairMiddleware to register any client-chosen accessKeyID with an empty ws.s3Secret. gofakes3 then verifies the request’s SigV4 signature against that same empty secret, while Server.auth passes the access key identifier as both the user and authentication value to the proxy without an independent per-identity secret. An unauthenticated network attacker can therefore choose an arbitrary access key, sign with an empty secret, and reach whatever backend the auth-proxy script resolves for that identity. This issue is fixed in version 1.75.1.
- Database specific
{ "cpes": [ "cpe:2.3:a:rclone:rclone:*:*:*:*:*:*:*:*" ], "severity": "Critical" }- References
Affected packages
Bitnami / rclone
Package
- Name
- rclone
- Purl
- pkg:bitnami/rclone
Severity
- 9.8 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator