How severe is CVE-2026-44405?

CVE-2026-44405 has a CVSS 3.x base score of 3.4, rated low severity. It is exploitable over an adjacent network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.

Is CVE-2026-44405 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (2nd percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-44405?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-44405 have an EU (EUVD) identifier?

Yes. CVE-2026-44405 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-27514.

When was CVE-2026-44405 published?

CVE-2026-44405 was published on 2026-05-06 and last updated on 2026-06-17.

CVE-2026-44405

CVE-2026-44405 is a low-severity vulnerability with a CVSS 3.x base score of 3.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-327.

Key facts

Severity: Low (CVSS 3.x base score 3.4)
EPSS exploit prediction: 0% (2nd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-27514
Weakness: CWE-327
Published: 2026-05-06
Last modified: 2026-06-17

Description

In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.

Frequently asked questions

What is CVE-2026-44405?: In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.
How severe is CVE-2026-44405?: CVE-2026-44405 has a CVSS 3.x base score of 3.4, rated low severity. It is exploitable over an adjacent network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2026-44405 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (2nd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-44405?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-44405 have an EU (EUVD) identifier?: Yes. CVE-2026-44405 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-27514.
When was CVE-2026-44405 published?: CVE-2026-44405 was published on 2026-05-06 and last updated on 2026-06-17.

References

Other CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities

CVE-2026-50086 — Critical (CVSS 10.0): The Aqara IAM/SSO gateway (gw-builder.aqara.com) exposes bidirectional AES round-trups against the platform's signing…
CVE-2026-21718 — Critical (CVSS 10.0): An authentication bypass vulnerability exists in Copeland XWEB Pro version 1.12.1 and prior, enabling any attackers to…
CVE-2025-54426 — Critical (CVSS 9.9): Polkadot Frontier is an Ethereum and EVM compatibility layer for Polkadot and Substrate. In versions prior to commit…
CVE-2024-51478 — Critical (CVSS 9.9): YesWiki is a wiki system written in PHP. Prior to 4.4.5, the use of a weak cryptographic algorithm and a hard-coded…
CVE-2026-28252 — Critical (CVSS 9.8): A Use of a Broken or Risky Cryptographic Algorithm vulnerability in Trane Tracer SC, Tracer SC+, and Tracer Concierge…
CVE-2025-13476 — Critical (CVSS 9.8): Rakuten Viber Cloak mode in Android v25.7.2.0g and Windows v25.6.0.0–v25.8.1.0 uses a static and predictable TLS…

Browse all CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities →