Is CVE-2026-79777 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-79777 being exploited in the wild.

How severe is CVE-2026-79777?

Low severity, with a CVSS score of 3.1, published 25 August 2026.

Which products and versions are affected?

github.com/rclone/rclone (Go) SEMVER:introduced=0,fixed=1.75.0; Rclone before 1.75.0.

Is there a fix for CVE-2026-79777?

Yes. github.com/rclone/rclone (Go): upgrade to 1.75.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-79777 attacked?

It is attacked over the network.

Am I affected by CVE-2026-79777?

Check whether you run github.com/rclone/rclone (Go) or Rclone at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-79777: rclone RC API information disclosure via stack traces

CVE-2026-79777 · Severity: low · CVSS 3.1 · Published 2026-08-25

rclone is a popular command-line tool for syncing files with cloud storage and managing remote filesystems. When the RC (Remote Control) API encounters errors, it can inadvertently expose detailed internal system information—including file paths, Go module versions, and memory addresses—to anyone with API access. An attacker with high privileges to the RC API can trigger these errors deliberately to leak sensitive debugging information that aids in further attacks.

Technologies: github.com/rclone/rclone (Go), Rclone. Vendors: Go, Rclone.

Quick answers

Is CVE-2026-79777 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-79777 being exploited in the wild.
How severe is CVE-2026-79777?: Low severity, with a CVSS score of 3.1, published 25 August 2026.
Which products and versions are affected?: github.com/rclone/rclone (Go) SEMVER:introduced=0,fixed=1.75.0; Rclone before 1.75.0.
Is there a fix for CVE-2026-79777?: Yes. github.com/rclone/rclone (Go): upgrade to 1.75.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-79777 attacked?: It is attacked over the network.
Am I affected by CVE-2026-79777?: Check whether you run github.com/rclone/rclone (Go) or Rclone at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/rclone/rclone (Go): upgrade to 1.75.0 or later
```
go get github.com/rclone/rclone@v1.75.0
```

Technical details

The vulnerability is an information disclosure flaw (CWE-209) in rclone's RC API error handling. When the RC API function runner catches a panic (in fs/rc/jobs/job.go:110-115), it captures the full output of Go's debug.Stack() and includes it verbatim in the JSON HTTP error response. This exposes file paths, Go runtime/module versions, goroutine IDs, memory addresses (ASLR leaks), and partial file contents to the API caller. An authenticated attacker with high privileges can trigger panics by sending malformed API requests (e.g., setting a config path to a non-INI file and calling dump). The vulnerability affects all rclone versions through v1.74.4 and is patched in v1.75.0 by returning generic error messages and logging full traces server-side only. Attack vector is network; no user interaction required.

Affected products

rclone rclone before 1.75.0

Identifiers

CVE-2026-79777
GHSA-gwfq-86j8-7qhv
GO-2026-6181

Timeline

2026-07-31: disclosed
2026-08-25: advisory
2026-08-25: patched: v1.75.0 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.