SSH authentication integrity reduction via SHA-1 RSA signatures
Published May 5, 2026 · Updated May 6, 2026
Cryptographic weakness in Paramiko through 4.0.0 before a448945 allows attackers to reduce SSH authentication integrity. RSAKey.HASHES maps the ssh-rsa and certificate identifiers to SHA-1, causing sign_ssh_data and verify_ssh_sig to create or accept deprecated signatures. The attacker must occupy an adjacent network position during SSH authentication, and the published consequence is limited to integrity.
Summary
What happened
Cryptographic weakness in Paramiko through 4.0.0 before a448945 allows attackers to reduce SSH authentication integrity. RSAKey.HASHES maps the ssh-rsa and certificate identifiers to SHA-1, causing sign_ssh_data and verify_ssh_sig to create or accept deprecated signatures. The attacker must occupy an adjacent network position during SSH authentication, and the published consequence is limited to integrity.
The record
- CVE
- CVE-2026-44405
- Published
- May 5, 2026
- Updated
- May 6, 2026
- Vendor
- Paramiko
- Product
- Paramiko
- Classifications
- CWE-327, T1557
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 5, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <a4489456b6f65281e172380cc4826cee5e851dbb
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo