Bug 2531542 (CVE-2026-88018) - CVE-2026-88018 rclone: rclone serve s3: --auth-proxy without --auth-key authenticates nobody - full SigV4 signature bypass
Summary: CVE-2026-88018 rclone: rclone serve s3: --auth-proxy without --auth-key authe...
Keywords:
Status: NEW
Alias: CVE-2026-88018
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2537399 2537401
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-10 16:14 UTC by OSIDB Bzimport
Modified: 2026-09-21 13:56 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-10 16:14:06 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.