Skip to main content
VulnerabilityPublished

CVE-2026-116188: rclone · Integer Overflow or Wraparound

Affects rcloneSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.75.2 when convenient.

Data as of 26 Oct 2026, 17:30 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.75.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade rclone to 1.75.2.

Affected software

ProductAffectedFixed in
rclonercloneAffected
  • >=1.75.0 <1.75.2
Fixed in
  • 1.75.2
Gorclonepkg:golang/rcloneOther threatsAffected
  • >=1.75.0 <1.75.2
Fixed in
  • 1.75.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade rclone to version 1.75.2 or later, where this integer overflow vulnerability has been fixed. Since patchAvailable is true and fixedVersions includes 1.75.2, applying this official fix fully mitigates the issue.

Description

An integer overflow vulnerability exists in rclone serve s3 versions 1.75.0 through 1.75.1 in the multipart reorder-memory accounting. This flaw allows attackers to bypass the configured buffer limit by opening two concurrent current-part PUT requests with large declared lengths, causing the signed int64 counter to wrap and enabling retention of out-of-order parts in memory, which can exhaust system resources.

References

Community reviews

Loading reviews…