rclone / rclone/rclone

need new release to fix log: avoid side effects by using own logger instance - fixes #8907#8908

Open
#9,457 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
59.9k
Forks
5.4k
Avg merge
2d 14h
Merged PRs (30d)
48

Description

The associated forum post URL from https://forum.rclone.org
What is the problem you are having with rclone?

Please create a new release to avoid side effects by using own logger instance (https://github.com/rclone/rclone/pull/8908), which resolves a Critical CVE-2026-41176(github.com/rclone/rclone). thanks so much

What is your rclone version (output from rclone version)
Which OS you are using and how many bits (e.g. Windows 7, 64 bit)
Which cloud storage system are you using? (e.g. Google Drive)
The command you were trying to run (e.g. rclone copy /tmp remote:tmp)
A log from the command with the -vv flag (e.g. output from rclone -vv copy /tmp remote:tmp)
How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing pull request #8908 and the related issues #8907 and #8908 to understand the logger-instance fix and its release status. Check the repository's release process and confirm that a release containing this fix is published; completion is a new release that includes the referenced change.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.