Is paramiko healthy, maintained, and safe?
No — paramiko carries 1 unpatched critical advisory and should not be adopted without a remediation plan.
The verdict
OSPulse scores paramiko at 55/100 (medium risk), computed deterministically from live PyPI release history, and the OSV vulnerability database. No — paramiko carries 1 unpatched critical advisory and should not be adopted without a remediation plan.
Its most recent release shipped on 9 May 2026 — 80 days ago — so development is clearly active. Across 151 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. PyPI doesn't expose a reliable maintainer count, so bus-factor isn't scored here — treat maintenance depth as unknown rather than assumed.
OSV lists 12 known advisories for paramiko, including 1 critical and 3 high. Open critical advisories are the strongest possible signal to pin to a patched version, replace, or fork before shipping. Each advisory is listed with its OSV/GHSA identifier below.
paramiko is usable but carries real signals — pin versions, watch for new advisories, and keep a fallback in mind. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own requirements.txt through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Known vulnerabilities (12)
Paramiko not properly checking authentication before processing other requests
Prefix Truncation Attack against ChaCha20-Poly1305 and Encrypt-then-MAC aka Terrapin
Paramiko Authentication Bypass vulnerability
Race Condition in Paramiko
Paramiko rsakey.py allows the SHA-1 algorithm
Paramiko Unsafe randomness usage may allow access to sensitive information
common.py in Paramiko 1.7.1 and earlier, when using threads or forked processes, does not properly use RandomPool, which allows one session to obtain sensitive information from another session by pred
transport.py in the SSH server implementation of Paramiko before 1.17.6, 1.18.x before 1.18.5, 2.0.x before 2.0.8, 2.1.x before 2.1.5, 2.2.x before 2.2.3, 2.3.x before 2.3.2, and 2.4.x before 2.4.1 do
Paramiko version 2.4.1, 2.3.2, 2.2.3, 2.1.5, 2.0.8, 1.18.5, 1.17.6 contains a Incorrect Access Control vulnerability in SSH server that can result in RCE. This attack appear to be exploitable via netw
In Paramiko before 2.10.1, a race condition (between creation and chmod) in the write_private_key_file function could allow unauthorized information disclosure.
Prefix Truncation Attack against ChaCha20-Poly1305 and Encrypt-then-MAC aka Terrapin
Paramiko rsakey.py allows the SHA-1 algorithm
Key facts
- Latest version
- v5.0.0
- Last release
- 9 May 2026 (80 days ago)
- Total releases
- 151
- First release
- 27 October 2010
- Package age
- 15.8 years
- Maintainers
- not exposed by PyPI
- Known advisories
- 12
- Confidence
- High
Frequently asked
Is paramiko still maintained?
Yes — paramiko released as recently as 9 May 2026 (80 days ago), so it is actively maintained.
Does paramiko have known security vulnerabilities?
Yes — OSV lists 12 advisories for paramiko, including 1 rated critical. See the advisory list on this page for the OSV/GHSA identifiers.
Is paramiko safe to use?
No — paramiko carries 1 unpatched critical advisory and should not be adopted without a remediation plan. OSPulse rates it 55/100 (medium risk) based on release recency, cadence and known vulnerabilities.
Other PyPI packages we've checked
paramiko is one package. What about the other hundreds in your tree?
Paste your own requirements.txt into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the PyPI registry & OSV.dev · snapshot generated 2026-07-28 · scores are deterministic and recomputed on each refresh.