Bug 2537399

Summary: CVE-2026-88018 rclone: rclone serve s3: --auth-proxy without --auth-key authenticates nobody - full SigV4 signature bypass [fedora-all]
Product: [Fedora] Fedora Reporter: Marian Rehak <mrehak>
Component: rcloneAssignee: Mikel Olasagasti Uranga <mikel>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: urgent    
Version: rawhideCC: go-sig, mikel
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["9811b395-133d-4f8f-b886-8e14d38af816"]}
Fixed In Version: rclone-1.75.2-1.fc44 rclone-1.75.2-1.fc45 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-10-21 01:03:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2531542    

Description Marian Rehak 2026-09-21 13:55:32 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.

Comment 1 Fedora Update System 2026-10-11 09:37:32 UTC
FEDORA-2026-7aab7a2bbe (rclone-1.75.2-1.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-7aab7a2bbe

Comment 2 Fedora Update System 2026-10-13 01:56:36 UTC
FEDORA-2026-7aab7a2bbe has been pushed to the Fedora 45 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-7aab7a2bbe`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-7aab7a2bbe

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2026-10-13 02:31:07 UTC
FEDORA-2026-e27d24d18c has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-e27d24d18c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-e27d24d18c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2026-10-21 01:03:38 UTC
FEDORA-2026-e27d24d18c (rclone-1.75.2-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2026-10-31 18:36:24 UTC
FEDORA-2026-7aab7a2bbe (rclone-1.75.2-1.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.