Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.0amended

rclone: WebDAV Credentials Survive a Same-Host HTTPS-to-HTTP Redirect

CVE-2026-79779GHSA-h4mf-4v27-hggj

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/rclone/rclone 1.75.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.0 · CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:H/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 · score source
EPSS
  • CVE-2026-79779: 0.11% estimated exploitation activity in the next 30 days; percentile 1.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

1. Summary WebDAV's default redirect handling can replay Basic authorization and configured Cookie headers over plaintext HTTP after a same-host HTTPS-to-HTTP redirect. This was reproduced through the real backend. Unlike the low-impact STS token in rclone's published S3 redirect advisory, Basic passwords and session cookies are complete reusable credentials, supporting a High rating when they grant normal WebDAV read/write access. The credible threat requires a legitimate endpoint, gateway, or accelerator to emit an unsafe redirect and an adjacent/on-path actor to observe the plaintext hop. A report should not rely on a malicious original WebDAV endpoint because that endpoint already receives the credentials. 2. Affected Assets & Attack Surface - Backend configuration/authentication: backend/webdav/webdav.go:127-139, 170-206, 440-530 - Shared redirect callback: lib/rest/rest.go:218-231 - HTTP client: fs/fshttp/http.go:311-329 - Credentials: Basic passwords, bearer authorization,…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-h4mf-4v27-hggj

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6197

  4. Revision 1 · created ·

    Published from osv record GHSA-h4mf-4v27-hggj

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-79779

Advisory: rclone: WebDAV Credentials Survive a Same-Host HTTPS-to-HTTP Redirect
IDs: CVE-2026-79779, GHSA-h4mf-4v27-hggj
Record: https://patchnext.com/advisories/cve-2026-79779 (revision 4, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/rclone/rclone 1.75.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/rclone/rclone: affected <= 1.74.0; fixed in 1.75.0

## Suggested inspection (read-only)
- Go github.com/rclone/rclone: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/rclone/rclone.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-h4mf-4v27-hggj (OSV record GHSA-h4mf-4v27-hggj lists affected ranges: Go github.com/rclone/rclone >=0 <1.75.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6197 (OSV record GO-2026-6197 lists affected ranges: Go github.com/rclone/rclone >=0 <1.75.0 (fixed))
- Verified: https://github.com/advisories/GHSA-h4mf-4v27-hggj (GitHub-reviewed advisory GHSA-h4mf-4v27-hggj lists affected ranges: Go github.com/rclone/rclone >=0 <=1.74.0)

Commands are suggestions: review each one before running it.

Loading voting…