Skip to main content
VulnerabilityPublished Updated

CVE-2026-44405: Duplicity · Paramiko rsakey.py allows the SHA-1 algorithm

Affects duplicitySource GCVE Database

0
Compare
Authoritative record:CVE-2026-44405· Low 3.4

Not known to be exploited · CVSS 3.4 Low : upgrade to 3.1.0_2 when convenient.

Data as of 1 Nov 2026, 02:07 UTC

CVSS 3.1 base score
3.4Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.1.0_2
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 31 Oct 2026.

What to do

Upgrade duplicity to 3.1.0_2.

Affected software

ProductAffectedFixed in
Homebrewduplicitypkg:brew/duplicityOther threatsAffected
  • <3.1.0_2
Fixed in
  • 3.1.0_2

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

AI-suggested

A patch is available in Duplicity version 3.1.0_2. Users should upgrade to this version or later to remediate the vulnerability. No additional mitigation steps are indicated.

Description

Duplicity versions prior to 3.1.0_2 use Paramiko's rsakey.py module which allows the use of the SHA-1 algorithm. This cryptographic choice is considered weak and deprecated. The vulnerability has a low CVSS score and does not impact confidentiality or availability but may allow limited integrity issues. A fix is available in version 3.1.0_2.

References

Community reviews

Loading reviews…