# CVE-2026-79776: rclone before 1.75.0 Authentication Bypass via pprof

> Attackers can access unauthenticated pprof endpoints in rclone to retrieve process arguments, exposing backend credentials.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** BIT-rclone-2026-79776, DEBIAN-CVE-2026-79776, GHSA-mfvx-7rcj-9m5g, GHSA-q353-w8p3-4cjq, MINI-jxmg-mm77-g7r5, MINI-r8v3-4qh3-69w2, UBUNTU-CVE-2026-79776

## What is CVE-2026-79776?

CVE-2026-79776 is a medium-severity vulnerability in rclone, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

rclone before 1.75.0 mounts the pprof debug handler as its own router route, bypassing the fail-closed authentication rule in the main handler. Attackers can access the /debug/pprof/cmdline endpoint unauthenticated to retrieve the full process argv including backend credentials.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-79776?

1 open source package ship an affected version, including rclone.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rclone` | Bitnami | All versions | 1.75.0 |

## How do I fix CVE-2026-79776?

Upgrade rclone to 1.75.0 or later.

## Is CVE-2026-79776 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-79776 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-79776 and fix it if it is affected.

What it is: CVE-2026-79776 is a medium-severity vulnerability in rclone, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-79776 exists.

Affected packages and fixed versions:
- rclone (Bitnami): affected all versions; fixed in 1.75.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-79776/ (Markdown: https://insights.sbomify.com/CVE-2026-79776/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-79776
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-79776
- OSV: https://osv.dev/vulnerability/CVE-2026-79776

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-79776/
Summaries are generated and may contain mistakes; the official description above is the record.