rclone before v1.75.0 Information Disclosure via RC API
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
cve-program · CVE-2026-79777
Publishedrclone before v1.75.0 includes full Go stack traces in RC API error responses when panics occur. Attackers can trigger panics to leak internal file paths, module versions, goroutine states, and memory addresses.
- Source published
- 25 Aug 2026 15:16:07 UTC
- Source modified
- 28 Aug 2026 22:25:36 UTC
- Observed here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 4.0 · 5.1 CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
CVSS 3.1 · 2.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
euvd · EUVD-2026-65535
Publishedrclone before v1.75.0 includes full Go stack traces in RC API error responses when panics occur. Attackers can trigger panics to leak internal file paths, module versions, goroutine states, and memory addresses.
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.
Original publisher date fields
datePublished: Aug 25, 2026, 3:16:07 PM
dateUpdated: Aug 28, 2026, 10:25:36 PM
- Source published
- Aug 25, 2026, 3:16:07 PM (timezone not stated)
- Source modified
- Aug 28, 2026, 10:25:36 PM (timezone not stated)
- Observed here
- 11 Nov 2026 16:09:54 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: euvd · ENISA EUVD · source terms and attribution apply. Source text is retained; field grouping and change labels are provided by ChangeIntel.
EUVD CVSS 4.0 · 5.1 CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
nvd · CVE-2026-79777
Publishedrclone before v1.75.0 includes full Go stack traces in RC API error responses when panics occur. Attackers can trigger panics to leak internal file paths, module versions, goroutine states, and memory addresses.
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.
Source analysis status: Awaiting Analysis
Weakness classifications: CWE-209
Original publisher date fields
published: 2026-08-25T16:17:29.520
lastModified: 2026-09-10T20:46:19.780
- Source published
- 25 Aug 2026 16:17:29 UTC
- Source modified
- 10 Sep 2026 20:46:19 UTC
- Observed here
- 25 Oct 2026 16:19:10 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: nvd · NIST NVD usage terms; underlying source attribution retained. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 4.0 · [email protected] · Secondary · 5.1 CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CVSS 3.1 · [email protected] · Secondary · 2.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
osv · GHSA-gwfq-86j8-7qhv
Published### 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`: ```go 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: ```bash 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/dump ``` Response includes: ```json { "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.
- Source published
- 5 Aug 2026 19:59:55 UTC
- Source modified
- 25 Sep 2026 14:25:40 UTC
- Observed here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
Publisher rating · LOW
osv · GO-2026-6181
PublishedVerbose stack trace disclosure in RC API error responses in github.com/rclone/rclone
- Source published
- 18 Aug 2026 16:38:10 UTC
- Source modified
- 25 Sep 2026 14:25:40 UTC
- Observed here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.