{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-41256 exists.","fix":"No fix has been published for CVE-2025-41256 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-41256 is a high-severity vulnerability in iterate GmbH Cyberduck, published on 25 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-41256 and fix it if it is affected.\n\nWhat it is: CVE-2025-41256 is a high-severity vulnerability in iterate GmbH Cyberduck, published on 25 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-41256 exists.\n\nAffected product: iterate GmbH Cyberduck. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-41256/ (Markdown: https://insights.sbomify.com/CVE-2025-41256/index.md)","id":"CVE-2025-41256","markdown":"https://insights.sbomify.com/CVE-2025-41256/index.md","name":"CVE-2025-41256","record":{"aliases":["GHSA-688c-vjrc-84rv","GHSA-qq37-7frg-jxx4"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Cloud storage client","requires_auth":"none","summary":"Attackers can bypass TLS certificate pinning in Cyberduck and Mountain Duck due to the use of the weak SHA-1 hash algorithm for certificate fingerprints.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"sba-research","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-328","name":"Use of Weak Hash"}],"description":"Cyberduck and Mountain Duck improper handle TLS certificate pinning for untrusted certificates (e.g., self-signed), since the certificate fingerprint is stored as SHA-1, although SHA-1 is considered weak.\n\nThis issue affects Cyberduck: through 9.1.6; Mountain Duck: through 4.17.5.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Cyberduck and Mountain Duck - Weak Hash Algorithm for Certificate Fingerprint","id":"CVE-2025-41256","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Suprema BioStar 2 Insecure Password Change","id":"CVE-2025-41257"},"packages":[],"prev":{"headline":"Cyberduck and Mountain Duck - Improper Certificate Store Handling","id":"CVE-2025-41255"},"products":["Cyberduck","Mountain Duck"],"published":"2025-06-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-06-25","vendors":["iterate GmbH"]},"summary":"Attackers can bypass TLS certificate pinning in Cyberduck and Mountain Duck due to the use of the weak SHA-1 hash algorithm for certificate fingerprints.","url":"https://insights.sbomify.com/CVE-2025-41256/"}