CVE-2025-41255: iterate Cyberduck · Incorrect Privilege Assignment
Affects iterate CyberduckSource CVE Database V5
Not known to be exploited · CVSS 8.0 High : upgrade to 9.1.7 soon.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.1.7
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 iterate-ch/cyberduck to 9.1.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubiterate-ch/cyberduckpkg:github/iterate-ch/cyberduckOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately audit and restrict the use of Cyberduck and Mountain Duck within the organization, especially on Windows endpoints. 2. Educate users about the risks of accepting untrusted or self-signed certificates and enforce policies to avoid manual acceptance of such certificates. 3. Implement endpoint protection solutions that monitor and alert on unauthorized modifications to the Windows Certificate Store, particularly additions of new certificates without administrative approval. 4. Use application whitelisting and privilege management to limit the ability of applications to alter certificate stores. 5. Employ network-level TLS inspection tools that can detect anomalous certificate chains or MITM attempts. 6. Where possible, replace Cyberduck and Mountain Duck with alternative clients that have verified secure certificate handling until patches are available. 7. 8. Enforce multi-factor authentication and strong access controls on systems that handle sensitive data to reduce the impact of potential interception. 9. Conduct regular security awareness training focusing on phishing and social engineering to mitigate the user interaction requirement for exploitation.
Description
Cyberduck and Mountain Duck improperly handle TLS certificate pinning for untrusted certificates (e.g., self-signed), unnecessarily installing it to the Windows Certificate Store of the current user without any restrictions. This issue affects Cyberduck through 9.1.6 and Mountain Duck through 4.17.5.