{"id":"BIT-rclone-2026-88018","revision":null,"records":[{"revision":"a7af0afda4ce4d67b38a3c53dd8e4127","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2026-88018","aliases":[],"title":"rclone serve s3: --auth-proxy without --auth-key authenticates nobody - full SigV4 signature bypass","description":"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.","state":0,"publishedAt":"2026-09-10T16:03:25.692+00:00","modifiedAt":"2026-09-10T16:14:29.874+00:00","affected":[{"ecosystem":"Vendor product","name":"rclone","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"rclone\",\n                    \"product\": \"rclone\",\n                    \"versions\": [\n                        {\n                            \"version\": \"< 1.75.1\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","score":9.8,"severity":"CRITICAL"}],"references":["https://github.com/rclone/rclone/security/advisories/GHSA-xwwr-4h3p-r22c","https://github.com/rclone/rclone/commit/90595f34f27f569be6b27c57fe5ab65057d323bd","https://github.com/rclone/rclone/releases/tag/v1.75.1"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-88018","license":"CVE Program Terms of Use","key":"cve-program:CVE-2026-88018","identifiers":["CVE-2026-88018"]},"retained":false,"historicalAffected":[]},{"revision":"9c45e010ef3841c491db84d339f12d63","observedAt":"2026-11-11T17:03:21.69+00:00","statement":{"source":"euvd","id":"EUVD-2026-75585","aliases":["CVE-2026-88018","GHSA-xwwr-4h3p-r22c"],"title":"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 cli…","description":"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.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","score":9.8,"severity":null}],"references":["https://github.com/rclone/rclone/security/advisories/GHSA-xwwr-4h3p-r22c","https://github.com/rclone/rclone/commit/90595f34f27f569be6b27c57fe5ab65057d323bd","https://github.com/rclone/rclone/releases/tag/v1.75.1"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-75585","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Sep 10, 2026, 4:03:25 PM","dateUpdated":"Sep 10, 2026, 4:14:29 PM"},"relatedAdvisories":[],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2026-75585","identifiers":["EUVD-2026-75585","CVE-2026-88018","GHSA-xwwr-4h3p-r22c"]},"retained":false,"historicalAffected":[]},{"revision":"be86b1ddc0f640b7bd290fe175c63b2c","observedAt":"2026-10-25T16:19:22.228+00:00","statement":{"source":"nvd","id":"CVE-2026-88018","aliases":[],"title":"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 cli…","description":"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.","state":0,"publishedAt":"2026-09-10T16:18:08.913+00:00","modifiedAt":"2026-09-14T20:01:05.627+00:00","affected":[],"metrics":[{"system":"CVSS 3.1 · security-advisories@github.com · Secondary","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","score":9.8,"severity":"CRITICAL"}],"references":["https://github.com/rclone/rclone/commit/90595f34f27f569be6b27c57fe5ab65057d323bd","https://github.com/rclone/rclone/releases/tag/v1.75.1","https://github.com/rclone/rclone/security/advisories/GHSA-xwwr-4h3p-r22c"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-88018","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Analyzed","weaknesses":["CWE-287","CWE-306"],"productCriteria":["cpe:2.3:a:rclone:rclone:*:*:*:*:*:*:*:*"],"sourceDates":{"published":"2026-09-10T16:18:08.913","lastModified":"2026-09-14T20:01:05.627"},"relatedAdvisories":[],"note":"NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON."},"key":"nvd:CVE-2026-88018","identifiers":["CVE-2026-88018"]},"retained":false,"historicalAffected":[]},{"revision":"da2d3c2847fb466f82eb0120393e38d7","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GHSA-xwwr-4h3p-r22c","aliases":["BIT-rclone-2026-88018","CVE-2026-88018","GO-2026-6462"],"title":"rclone serve s3: --auth-proxy without --auth-key authenticates nobody - full SigV4 signature bypass","description":"### Summary\n`rclone serve s3`'s handler chain, when `--auth-proxy` is configured, is (outermost first): `authPairMiddleware` -> `proxyAuthMiddleware` -> gofakes3's own SigV4-verifying handler.\n\n`authPairMiddleware` parses the accessKeyID straight out of the incoming request's own `Authorization` header (entirely client-controlled) and registers `{accessKey: ws.s3Secret}` into gofakes3's shared credential store via `AddAuthKeys`, for EVERY access key any client presents - not just ones previously known to the server. `ws.s3Secret` defaults to `\"\"` whenever `--auth-key` is not set, which the `--auth-proxy` documentation (and the reference `bin/test_proxy.py`) presents as a complete, standalone authentication mechanism requiring no other flag - matching how it's used for `serve webdav`/`ftp`/`sftp`.\n\ngofakes3's SigV4 verification then checks the request's signature against exactly the secret `authPairMiddleware` just registered for that same client-chosen key. An empty string is a valid HMAC key, so a caller can trivially compute a correct SigV4 signature for ANY access key ID of their choosing using an empty secret, and verification passes.\n\nCrucially, the auth-proxy script never receives a real secret to verify against, for S3 specifically: `Server.auth()` calls `w.proxy.Call(md5(accessKeyID), accessKeyID, false, r.RemoteAddr)` - passing the access key ID itself as BOTH the hashed \"user\" and the raw \"auth\"/password fields. Contrast with `serve webdav`/`ftp`/`sftp`, whose proxy integration passes the client's actual typed password (see `bin/test_proxy.py`, which forwards it into a backing SFTP login for real verification). For S3, no independent secret is ever transmitted to the proxy script at all, so no script - however carefully written - can distinguish a legitimate holder of an access key ID from an attacker who merely picked the same string.\n\nNet effect: with `--auth-proxy` configured and `--auth-key` not also set (the configuration the feature is documented to support standalone), SigV4 signature verification authenticates nobody.\n\n### Details\nVulnerable code (before fix):\n```go\nfunc authPairMiddleware(next http.Handler, ws *Server) http.Handler {\n\treturn http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {\n\t\taccessKey, _ := parseAccessKeyID(r)\n\t\tauthPair := map[string]string{accessKey: ws.s3Secret}\n\t\tws.faker.AddAuthKeys(authPair)\n\t\tnext.ServeHTTP(w, r)\n\t})\n}\n```\n\n### PoC\nBuilt and signed a request by hand (via the vendored `github.com/aws/aws-sdk-go-v2/aws/signer/v4`) using a freshly-random access key ID never configured or returned by anything, with `SecretAccessKey: \"\"`, against a real `rclone serve s3 --auth-proxy <script>` instance with no `--auth-key` set:\n```\nstatus=200\n<ListAllMyBucketsResult>...<Bucket><Name>mybucket</Name>...\n```\nA fully authenticated, successful bucket listing, with zero prior credential knowledge.\n\n### Impact\nAny network-reachable, unauthenticated attacker who knows (or discovers) that a target is running `rclone serve s3 --auth-proxy` without `--auth-key` can choose an arbitrary access key ID, sign a request against an empty secret, and be treated as an authenticated user by the auth-proxy script - reaching whatever backend that script resolves the chosen identity to. No credentials, prior access, or user interaction of any kind are required.\n\n### Fix\nRefuse to start `rclone serve s3` when `--auth-proxy` is set without `--auth-key`, rather than silently falling back to a signature check that authenticates nobody:\n```go\nif proxyOpt.AuthProxy != \"\" && len(opt.AuthKey) == 0 {\n\treturn nil, errors.New(\"serve s3: --auth-proxy requires --auth-key to also be set (SigV4 has no other way to verify a signature for a dynamically-proxied identity)\")\n}\n```\nNote this is a minimal fix for the zero-knowledge bypass; once `--auth-key` is also set, every access key ID still shares that one static secret for signature-verification purposes (a caller who knows it can request any identity from the proxy script) - a narrower, pre-existing limitation flagged for awareness but not changed here, since a complete fix needs the auth-proxy wire protocol to carry a per-identity secret for S3 specifically (a larger design change).","state":0,"publishedAt":"2026-09-10T22:49:07+00:00","modifiedAt":"2026-09-17T17:41:03.6236126+00:00","affected":[{"ecosystem":"Go","name":"github.com/rclone/rclone","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"1.75.1"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"CRITICAL"}],"references":["https://github.com/rclone/rclone/security/advisories/GHSA-xwwr-4h3p-r22c","https://nvd.nist.gov/vuln/detail/CVE-2026-88018","https://github.com/rclone/rclone/commit/90595f34f27f569be6b27c57fe5ab65057d323bd","https://github.com/rclone/rclone","https://github.com/rclone/rclone/releases/tag/v1.75.1"],"sourceUrl":"https://github.com/advisories/GHSA-xwwr-4h3p-r22c","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-xwwr-4h3p-r22c","identifiers":["GHSA-xwwr-4h3p-r22c","BIT-rclone-2026-88018","CVE-2026-88018","GO-2026-6462"]},"retained":false,"historicalAffected":[]},{"revision":"1df60d8350314d9c8e93f99f9bf89105","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GO-2026-6462","aliases":["BIT-rclone-2026-88018","CVE-2026-88018","GHSA-xwwr-4h3p-r22c"],"title":"rclone serve s3: --auth-proxy without --auth-key authenticates nobody - full SigV4 signature bypass in github.com/rclone/rclone","description":"rclone serve s3: --auth-proxy without --auth-key authenticates nobody - full SigV4 signature bypass in github.com/rclone/rclone","state":0,"publishedAt":"2026-09-16T16:56:29+00:00","modifiedAt":"2026-09-17T17:41:03.6236126+00:00","affected":[{"ecosystem":"Go","name":"github.com/rclone/rclone","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"1.75.1"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[],"references":["https://github.com/rclone/rclone/security/advisories/GHSA-xwwr-4h3p-r22c","https://nvd.nist.gov/vuln/detail/CVE-2026-88018","https://github.com/rclone/rclone/commit/90595f34f27f569be6b27c57fe5ab65057d323bd","https://github.com/rclone/rclone/releases/tag/v1.75.1"],"sourceUrl":"https://osv.dev/vulnerability/GO-2026-6462","license":"OSV · upstream source license applies","key":"osv:GO-2026-6462","identifiers":["GO-2026-6462","BIT-rclone-2026-88018","CVE-2026-88018","GHSA-xwwr-4h3p-r22c"]},"retained":false,"historicalAffected":[]}],"coverage":[{"source":"cisa-kev:global","scope":"Complete CISA KEV catalog; all vendors. Missing entries do not establish absence of exploitation.","generation":"2026-11-13T15:58:45.9370155+00:00","complete":true,"records":1779,"lastAttemptAt":"2026-11-13T15:58:45.9370155+00:00","lastSuccessAt":"2026-11-13T15:58:46.132012+00:00","error":null,"lastVerifiedAt":"2026-11-13T15:58:46.1320133+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"cve-program","scope":"Official CVE Program baseline and cumulative hourly delta; all vendors, published and rejected records","generation":"cve-d8fa82e95fdb59244e2f635e667ba17f0796ca0a4f1f4bb8cc31febcd660b76c-f30f6521a28a70c55d687bf12eb3f6661f9fd2c736c2dd12332e36b75810d702","complete":true,"records":425437,"lastAttemptAt":"2026-11-13T15:56:59.344935+00:00","lastSuccessAt":"2026-11-13T15:56:59.1857541+00:00","error":null,"lastVerifiedAt":"2026-11-13T15:56:59.344935+00:00","snapshotPublishedAt":"2026-11-13T15:27:01+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"euvd","scope":"Rolling EUVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global EUVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-9bf03eaddbbb43da9055fdaab85603b8","complete":false,"records":13797,"lastAttemptAt":"2026-11-13T16:08:28.1937422+00:00","lastSuccessAt":"2026-11-13T16:08:27.176+00:00","error":"694 identifier lookups failed; latest failures include AccessDenied (HTTP 403). Other identifiers were checked independently.","lastVerifiedAt":"2026-11-13T16:08:27.176+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":12793,"expectedIdentifiers":13850,"failedIdentifiers":694},{"source":"first-epss:nuget","scope":"FIRST EPSS for explicit CVE aliases in the collected public NuGet archive. Not a global EPSS backfill.","generation":"2026-11-13T15:58:45.9370155+00:00","complete":true,"records":1123,"lastAttemptAt":"2026-11-13T15:58:45.9370155+00:00","lastSuccessAt":"2026-11-13T15:58:46.1332262+00:00","error":null,"lastVerifiedAt":"2026-11-13T15:58:46.1332266+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"nvd","scope":"Rolling NVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global NVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-c4db44c2f8494656b34b99b9689fe3fd","complete":true,"records":13797,"lastAttemptAt":"2026-11-13T15:58:46.6969095+00:00","lastSuccessAt":"2026-11-13T14:58:49.069+00:00","error":null,"lastVerifiedAt":"2026-11-13T14:58:49.069+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13850,"expectedIdentifiers":13850,"failedIdentifiers":0},{"source":"osv:Go","scope":"Complete OSV Go ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"go-93e76d404e1aeb6a7e8902f5ffa06211fc86dea3b1958e297abb2668aa5e6e8c","complete":true,"records":9952,"lastAttemptAt":"2026-11-13T15:58:41.8794803+00:00","lastSuccessAt":"2026-11-12T23:19:15.5239119+00:00","error":null,"lastVerifiedAt":"2026-11-13T15:58:41.8794803+00:00","snapshotPublishedAt":"2026-11-12T23:03:02+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:NuGet","scope":"Complete OSV NuGet ecosystem archive, including GitHub Advisory Database records; NuGet version matching only","generation":"nuget-4d60731753a2f72e455d1086e7203d0ef10843936dcc1cf2b45135e2caa204b0","complete":true,"records":2012,"lastAttemptAt":"2026-11-13T15:56:59.4004595+00:00","lastSuccessAt":"2026-11-12T18:16:50.7862525+00:00","error":null,"lastVerifiedAt":"2026-11-13T15:56:59.4004595+00:00","snapshotPublishedAt":"2026-11-12T17:48:11+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:crates.io","scope":"Complete OSV crates.io ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"crates.io-f7b4a39cba128839548000e6d1d86fef7e48dd6f19f8e345c343f4aa28de8b91","complete":true,"records":3146,"lastAttemptAt":"2026-11-13T15:58:45.8997644+00:00","lastSuccessAt":"2026-11-13T15:58:45.7257812+00:00","error":null,"lastVerifiedAt":"2026-11-13T15:58:45.8997644+00:00","snapshotPublishedAt":"2026-11-13T15:48:17+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:npm","scope":"Complete OSV npm ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"npm-be73125c24c129574dee5d5172fc21e3836479148a86b896460503bb167ac981","complete":true,"records":231774,"lastAttemptAt":"2026-11-13T15:58:41.7528474+00:00","lastSuccessAt":"2026-11-13T15:58:40.2393964+00:00","error":null,"lastVerifiedAt":"2026-11-13T15:58:41.7528474+00:00","snapshotPublishedAt":"2026-11-13T15:33:10+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}