Authenticated information disclosure via panic stack traces
Published Aug 25, 2026 · Updated Aug 28, 2026
Information disclosure in rclone before 1.75.0 allows remote authenticated users to read runtime details through RC API errors. The job runner places debug.Stack output in its error field after recovering a panic, and the field is returned in the HTTP JSON response. Exploitation requires high-privilege RC API access and a request that triggers a recovered panic; exposed data includes paths, versions, goroutine state, memory addresses, and an unparsable file line.
Summary
What happened
Information disclosure in rclone before 1.75.0 allows remote authenticated users to read runtime details through RC API errors. The job runner places debug.Stack output in its error field after recovering a panic, and the field is returned in the HTTP JSON response. Exploitation requires high-privilege RC API access and a request that triggers a recovered panic; exposed data includes paths, versions, goroutine state, memory addresses, and an unparsable file line.
The record
- CVE
- CVE-2026-79777
- Published
- Aug 25, 2026
- Updated
- Aug 28, 2026
- Vendor
- Rclone
- Product
- rclone
- Classifications
- CWE-209, T1082
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.75.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- RC API panic stack-trace disclosure PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo