CVE-2026-44405: Paramiko rsakey.py allows the SHA-1 algorithm
Affects paramikoSource GCVE Database
Not known to be exploited · CVSS 3.4 Low.
Data as of 27 Oct 2026, 00:07 UTC
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 May 2026
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPIparamiko | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.
References
- nvd.nist.gov/vuln/detail/CVE-2026-44405 (opens in a new tab)
- github.com/paramiko/paramiko/commit/a4489456b6f65281e172380cc4826cee5e851dbb (opens in a new tab)
- github.com/paramiko/paramiko (opens in a new tab)
- ostif.org/wp-content/uploads/2026/05/25-11-2415-REP_paramiko-security-audit_v1.1.pdf (opens in a new tab)