GHSA-gwfq-86j8-7qhv: rclone: Verbose Stack Trace Disclosure in RC API Error Responses
Summary When an RC API call triggers a panic (recovered by the job runner), the full Go stack trace is included in the JSON error response. This leaks internal file paths, Go module versions, goroutine state, and memory addresses to the API caller. Details The panic recovery in fs/rc/jobs/job.go:110-115: The full debug.Stack() output is placed into j.Error, which is then returned in the HTTP response JSON.
Published Aug 5, 2026
Affected packages
github.com/rclone/rclone
- Ecosystem
- Go
- Affected
- <= 1.74.4
- Fixed in
- 1.75.0
- Check
go list -m github.com/rclone/rclone
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
When an RC API call triggers a panic (recovered by the job runner), the full Go stack trace is included in the JSON error response. This leaks internal file paths, Go module versions, goroutine state, and memory addresses to the API caller.
Details
The panic recovery in fs/rc/jobs/job.go:110-115:
func (j *Job) run(ctx context.Context, fn rc.Func, in rc.Params) {
defer func() {
if r := recover(); r != nil {
j.mu.Lock()
j.EndTime = time.Now()
j.Error = fmt.Sprintf("panic received: %v \n%s", r, string(debug.Stack()))
// ...
}
}()The full debug.Stack() output is placed into j.Error, which is then returned in the HTTP response JSON.
PoC
Trigger a parse error by setting config path to a non-INI file, then calling dump:
curl -s -X POST http://localhost:5572/config/setpath \
-H "Content-Type: application/json" \
-d '{"path":"/etc/hostname"}'
curl -s -X POST http://localhost:5572/config/dumpResponse includes:
{
"error": "panic received: fatal error: Failed to load config file \"/etc/hostname\": could not parse line: ... \ngoroutine 9 [running]:\nruntime/debug.Stack()\n\truntime/debug/stack.go:26 +0x64\ngithub.com/rclone/rclone/fs/rc/jobs.(*Job).run.func1()\n\tgithub.com/rclone/rclone/fs/rc/jobs/job.go:112 +0x34\n...",
"status": 500
}Disclosed information includes:
- Full filesystem paths (
github.com/rclone/rclone/fs/config/config.go:377) - Go module versions (
github.com/go-chi/chi/[email protected]) - Go runtime version (from binary)
- Goroutine IDs and states
- Memory addresses (ASLR leak)
- File contents (first unparseable line of the target file)
Tested and confirmed on rclone v1.74.4.
Impact
Information disclosure that aids exploitation of other vulnerabilities. Stack traces reveal internal architecture, dependency versions (useful for known-CVE targeting), and memory layout. The error message also leaks partial file contents (the first line that fails INI parsing), which can be used alongside the arbitrary file read finding as a complementary file read primitive for non-INI files.
Affected Versions
All versions with RC API support through at least v1.74.4.
Remediation
Return a generic error message to the API caller. Log the full stack trace server-side only. Strip debug.Stack() from HTTP responses.
Credited to SnailSploit, ncw.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-88013
rclone: http backend forwards custom/auth headers to a different host on redirect
low3.7Sep 10, 2026CVE-2026-88014
rclone archive/zip: Zip Slip via unsanitized zip entry names lets a malicious archive escape its own namespace
medium6.3Sep 10, 2026CVE-2026-88015
rclone local: crafted Range request against a translated symlink panics (DoS)
medium5.3Sep 10, 2026CVE-2026-88016
rclone: Directory metadata (chmod/chown/chtimes) applied through a planted symlink in rclone local --links escapes the destination
medium6.5Sep 10, 2026CVE-2026-88017
rclone: FTP cross-session auth-proxy backend confusion
high7.3Sep 10, 2026CVE-2026-88018
rclone serve s3: --auth-proxy without --auth-key authenticates nobody - full SigV4 signature bypass
critical9.8Sep 10, 2026
