Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.0amended

rclone: Infinite Scale TUS Creation Transport Error Causes a Nil-Response Panic

CVE-2026-79778GHSA-3x6r-wxxg-53vv

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:N/AC:H/AT:P/PR:N/UI:P/VC:N/VI:N/VA:H/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-79778: 0.29% estimated exploitation activity in the next 30 days; percentile 21.13 (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 A transport failure during the initial Infinite Scale TUS creation POST can return (nil response, non-nil error). Rclone dereferences the nil response before processing the error and panics. The production CreateUploader path reproduced the crash against a closed endpoint. The security case is deployment-dependent. A one-shot upload already fails when its endpoint resets, while RC jobs recover panics in fs/rc/jobs/job.go and return a job error. The incremental denial of service is strongest in a long-lived VFS mount or concurrent/multi-remote CLI process where the upload runs in an unrecovered goroutine and the panic terminates unrelated work. 2. Affected Assets & Attack Surface - Verified rclone revision: a0c09f1381ae93e2a9a33c529d170186c61ad058 (v1.74.0-240-ga0c09f138) - Current-master check: backend/webdav/tus.go was unchanged at master commit 961266888fe797390c535386f3b3aa46f4853602 on 2026-07-18 - Response evaluation: backend/webdav/tus.go:45-59 - Creation path:…

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

    Amended from ghsa record GHSA-3x6r-wxxg-53vv

  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-6183

  4. Revision 1 · created ·

    Published from osv record GHSA-3x6r-wxxg-53vv

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-79778

Advisory: rclone: Infinite Scale TUS Creation Transport Error Causes a Nil-Response Panic
IDs: CVE-2026-79778, GHSA-3x6r-wxxg-53vv
Record: https://patchnext.com/advisories/cve-2026-79778 (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-3x6r-wxxg-53vv (OSV record GHSA-3x6r-wxxg-53vv lists affected ranges: Go github.com/rclone/rclone >=0 <1.75.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6183 (OSV record GO-2026-6183 lists affected ranges: Go github.com/rclone/rclone >=0 <1.75.0 (fixed))
- Verified: https://github.com/advisories/GHSA-3x6r-wxxg-53vv (GitHub-reviewed advisory GHSA-3x6r-wxxg-53vv lists affected ranges: Go github.com/rclone/rclone >=0 <=1.74.0)

Commands are suggestions: review each one before running it.

Loading voting…