Is github.com/ncw/rclone 1.66 vulnerable?

Go · 1 release from 1.66.0 to 1.66.0 · latest github.com/ncw/rclone is 1.76.0 · checked 20 Nov 2026

Yes: 2 known advisories

Yes. github.com/ncw/rclone 1.66.0, the last 1.66 release, is affected by 2 known security advisories (2 low), including CVE-2026-49980, CVE-2026-41179. At least one has no fixed release yet.

Is your project on an affected github.com/ncw/rclone?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting github.com/ncw/rclone 1.66.0

  • LowCVE-2026-49980GO-2026-559611 Aug 2026

    Unauthenticated command execution in rclone rcd via inline remotes in github.com/rclone/rclone

    Affected
    >=1.46.0
    Fixed in
    No fix released
  • LowCVE-2026-41179GO-2026-546611 Aug 2026

    Unauthenticated backend instantiation in github.com/rclone/rclone

    Affected
    >=1.48.0
    Fixed in
    No fix released

Which of your client projects are still on github.com/ncw/rclone 1.66?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/ncw/rclone version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other github.com/ncw/rclone versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.