CVE-2026-79777

lowpriority · track · 11EPSS 0.003 · 22 %ileUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
0.30% (22nd) EPSS
CVSS 2.7 · low
Is it mine?
2 products
Check your exposure
Who says so?
1 sources
osv

EPSS · scored 2026-10-27

rclone 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.

01

cvss

Technical severity, 0–10. One row per scoring source.

5.1
010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 1.2–5.1

v3.12.7lowCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:Nprimary · disclosure@vulncheck.comexploitability 1.2 · impact 1.4
v3.12.7lowCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:Nsecondary · OSV
v4.05.1mediumCVSS: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:Xsecondary · disclosure@vulncheck.com
v4.01.2lowCVSS: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:U/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:Xsecondary · CVSS-BT (t0sche)
02

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: poc · Automatable: no · Technical Impact: partialcoordinatorcisa_ssvcUS
03

weaknesses

The CWE weakness classes this flaw belongs to.

04

affected products (2)

Products and version ranges known to be affected.

05

advisories (3)

Vendor and ecosystem advisories describing this.

  • GHSA-gwfq-86j8-7qhvrclone: Verbose Stack Trace Disclosure in RC API Error Responses2026-08-05ghsa · osvUS

    ### 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/v5@v5.2.5`) - 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.

  • BIT-rclone-2026-79777rclone before v1.75.0 Information Disclosure via RC API2026-09-25vendor · osvUS

    rclone 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.

  • GO-2026-6181Verbose stack trace disclosure in RC API error responses in github.com/rclone/rclone2026-08-18vendor · osvUS

    Verbose stack trace disclosure in RC API error responses in github.com/rclone/rclone

06

also known as (3)

Other names and identifiers for this entity.

07

sources

Which sources assert this record, and when.

published 2026-08-25modified 2026-08-28
08

references (2) nvd

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan