HighGHSA-f8q4-jwww-x3wvCVE-2022-24302PYSEC-2022-166

Race Condition in Paramiko

Published 19 Mar 2022 · Updated 20 Dec 2025

Is your project on an affected paramiko?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=2.10.0 <2.10.1
Fixed in
2.10.1
Update to the fixed version for your release line, for example:pip install 'paramiko>=2.10.1'
Affected
>=2.9.0 <2.9.3
Fixed in
2.9.3
Update to the fixed version for your release line, for example:pip install 'paramiko>=2.9.3'

Details

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.

Is GHSA-f8q4-jwww-x3wv in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected paramiko, and gives you the command that fixes it.

More advisories for paramiko

  • LowCVE-2026-44405Paramiko rsakey.py allows the SHA-1 algorithm · 6 May 2026
  • MediumCVE-2023-48795Prefix Truncation Attack against ChaCha20-Poly1305 and Encrypt-then-MAC aka Terrapin · 18 Dec 2023
  • HighCVE-2008-0299Paramiko Unsafe randomness usage may allow access to sensitive information · 1 May 2022
  • HighCVE-2018-1000805Paramiko Authentication Bypass vulnerability · 10 Oct 2018
  • CriticalCVE-2018-7750Paramiko not properly checking authentication before processing other requests · 12 Jul 2018
paramiko security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.