Quick answers
- Is CVE-2026-116194 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116194 being exploited in the wild.
- How severe is CVE-2026-116194?
- Medium severity, with a CVSS score of 6.8, published 25 October 2026.
- Which products and versions are affected?
- Rclone 1.52.0 to 1.75.1.
- Is there a fix for CVE-2026-116194?
- Yes: fixed in 1.75.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116194 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116194?
- Check whether you run Rclone at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.75.2
Technical details
The pCloud backend disables OAuth state validation (StateBlankOK: true) and accepts unauthenticated callback requests on localhost:53682, then trusts the hostname parameter from the callback to configure the API endpoint. An attacker can craft a cross-site request from a web page visited during authorization to plant their own token and API host, causing subsequent rclone operations to contact the attacker's server instead of pCloud. The vulnerability is preceded by missing CSRF protection on the localhost OAuth callback handler.
Affected products
- Rclone Rclone 1.52.0 to 1.75.1
Timeline
- 2026-10-09: disclosed
- 2026-10-25: advisory