# Paramiko rsakey.py allows the SHA-1 algorithm

Advisory record · `GHSA-r374-rxx8-8654`

- **Identifiers:** `GHSA-r374-rxx8-8654` · `CVE-2026-44405` · `PYSEC-2026-2858`
- **State:** Confirmed
- **Severity:** CVSS 3.4 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-327](https://cwe.mitre.org/data/definitions/327.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 6 May 2026
- **Updated:** 7 Nov 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 6 May 2026, 00:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `paramiko` (PyPI): affected `<5.0.0`; fixed in `5.0.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Paramiko versions through 4.0.0 are affected. The rsakey.py module allows the SHA-1 algorithm, and the source gives few details about how this could be exploited. No fix is listed.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 3.4 Low, CVSS 3.1: `CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N`, from CNA (mitre)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0011, the 1st percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 6 May 2026, 00:31 UTC: [Confirmed by GitHub Advisory Database](https://github.com/advisories/GHSA-r374-rxx8-8654)
- 31 Oct 2026, 14:11 UTC: First seen by agentprime
- 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-r374-rxx8-8654)

## Sources

- [GitHub Advisory Database: GHSA-r374-rxx8-8654](https://github.com/advisories/GHSA-r374-rxx8-8654)
- [OSV: GHSA-r374-rxx8-8654](https://osv.dev/vulnerability/GHSA-r374-rxx8-8654)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-44405>
- <https://github.com/paramiko/paramiko/commit/a4489456b6f65281e172380cc4826cee5e851dbb>
- <https://github.com/advisories/GHSA-r374-rxx8-8654>
- <https://github.com/paramiko/paramiko>
- <https://github.com/pypa/advisory-database/tree/main/vulns/paramiko/PYSEC-2026-2858.yaml>
- <https://ostif.org/wp-content/uploads/2026/05/25-11-2415-REP_paramiko-security-audit_v1.1.pdf>
- <https://pypi.org/project/paramiko>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-r374-rxx8-8654>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-r374-rxx8-8654/>. Everything for agents: <https://agentprime.io/llms.txt>.