Rclone credential leak in swift, NetStorage, Seafile backends
Affects rclone before 1.76.0 using the swift, netstorage or seafile backend. Fixed in 1.76.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.76.0
- Who is exposed
- Not reported
Summary
Written by a model
rclone before 1.76.0 leaks credentials in its swift, netstorage and seafile backends, which follow HTTP redirects using Go's default policy: swift and netstorage send auth headers or passwords on cross-host or HTTPS-to-HTTP redirects, and seafile sends API tokens or passwords on same-host HTTPS-to-HTTP redirects. Attackers receiving or observing a redirect issued by the configured endpoint can capture these credentials to access storage or replay signed requests.
Who should check
Teams running rclone before 1.76.0 with the swift, netstorage or seafile backends, or redirecting those endpoints through proxies, load balancers or CDNs. Go module github.com/rclone/rclone.
“rclone before 1.76.0 leaks credentials in its swift, netstorage and seafile backends”
What to do
Upgrade to a fixed version: 1.76.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134353 (rclone before 1.76.0 Credential Leak via Swift, NetStorage and Seafile Redirects), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134353 (entry last updated 2026-11-21):
Affected:
- Go package github.com/rclone/rclone: fixed in 1.76.0
Fixed versions: 1.76.0.
Conditions (all must be true for the bug to be hit):
- Affects rclone before 1.76.0 using the swift, netstorage or seafile backend. (source: https://www.vulncheck.com/advisories/rclone-before-1.76.0-credential-leak-via-swift-netstorage-and-seafile-redirects)
- Seafile leaks credentials on a same-host redirect from HTTPS to HTTP. (source: https://github.com/rclone/rclone/security/advisories/GHSA-m97j-7x65-wh93)
- Swift and netstorage leak credentials on cross-host or HTTPS to HTTP redirects. (source: https://github.com/rclone/rclone/security/advisories/GHSA-m97j-7x65-wh93)
- The redirect must be issued by the configured endpoint, or by something in front of it that holds a valid certificate for it. (source: https://github.com/rclone/rclone/security/advisories/GHSA-m97j-7x65-wh93)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134353 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134353 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/rclone/rclone/security/advisories/GHSA-m97j-7x65-wh93
- https://www.vulncheck.com/advisories/rclone-before-1.76.0-credential-leak-via-swift-netstorage-and-seafile-redirects
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134353
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134353"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Affects Go packages
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 78 if added to CISA KEV
- Would score about 73 if CISA's SSVC rates exploitation active
- Would score about 38 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · rclone/rclone · Advisory GHSA-m97j-7x65-wh93 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134353 |
| Record | NVD · CVE-2026-134353 |
| Other links 1 | |
| Link | vulncheck.com · advisories/rclone-before-1.76.0-credential-leak-via-swift-netstorage-and-seafile-redirects |
Questions about CVE-2026-134353
Is CVE-2026-134353 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
rclone leaks credentials in its swift, netstorage and seafile backends when it follows a redirect. Swift and netstorage leak them on cross-host redirects or HTTPS to HTTP redirects, and seafile leaks them on same-host HTTPS to HTTP redirects. Whoever receives the leaked credentials can list, read, write and delete objects in the whole account until the token expires, or use long-lived keys or passwords, or replay a signed request within its time window.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134353?
github.com/rclone/rclone (Go): before 1.76.0.
Source: cve.now feed data
Am I affected, and how do I check?
Versions of rclone before 1.76.0 that use the swift, netstorage or seafile backend are affected. To check, run rclone version to see the installed version and review the type setting of each remote in the rclone configuration to see which backend it uses. The redirect must come from the configured endpoint, or from something in front of it that holds a valid certificate for that endpoint.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134353?
Upgrade rclone to 1.76.0 or later, which contains the fix.
Source: vulncheck.com, github.com
Related
- CVE-2026-134352Rclone 1.51.0 before 1.76.0 Authentication Bypass via serve sftp Auth-Proxy Cache
- CVE-2026-88044rclone: RC per-server auth-proxy bypass
- CVE-2026-116191Rclone before 1.75.2 Path Traversal via serve webdav MKCOL
- CVE-2026-116192rclone from 1.37 before 1.74.2 SSRF via --rc-serve scheme-relative remote roots
- CVE-2026-116189rclone 1.55.0 before 1.75.2 selfupdate Signature Verification Bypass via SHA256SUMS
- CVE-2026-116194Rclone 1.52.0 before 1.75.2 CSRF via pCloud OAuth Callback
No corrections so far. Something wrong on this page? Report an error.