How severe is CVE-2022-24302?

CVE-2022-24302 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-24302?

CVE-2022-24302 affects the following packages: paramiko (PyPI), paramiko (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2022-24302?

Update paramiko to 2.10.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24302 is resolved across your whole dependency graph.

How do I detect CVE-2022-24302 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for paramiko, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-24302 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2022-24302 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-24302, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-24302?

CVE-2022-24302 has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 82th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-24302?

CVE-2022-24302 is classified as CWE-362 (CWE-362). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-24302 published, and has it been updated?

CVE-2022-24302 was published on March 17, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2022-24302 — paramiko

MEDIUMFix: paramiko/paramiko@4c491e2

CVE-2022-24302 is a medium-severity (CVSS 5.9) CWE-362 vulnerability in paramiko. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for paramiko — see the affected versions and patch details below.

Race Condition in Paramiko

Also known asGHSA-f8q4-jwww-x3wvPYSEC-2022-166

Published

Mar 17, 2022

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐍paramiko🐍paramiko

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`paramiko`	≥ 2.10.0&&< 2.10.1	2.10.1`pip install --upgrade 'paramiko==2.10.1'`
🐍PyPI	`paramiko`	≥ 2.9.0&&< 2.9.3	2.9.3`pip install --upgrade 'paramiko==2.9.3'`

Affected Products

3 products · 6 configurations

debian linuxdebian

2 versions

9.010.0

fedorafedoraproject

3 versions

343536

Application

paramikoparamiko

< 2.10.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In Paramiko before 2.10.1, a race condition (between creation and chmod)…

github.comNVDMar 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for paramiko, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update paramiko to 2.10.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24302 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat OpenStack Platform 16.1	`python-paramiko-0:2.4.2-8.el8ost`	RHSA-2022:8863
Red Hat OpenStack Platform 16.2	`python-paramiko-0:2.4.2-8.el8ost`	RHSA-2022:8845
Red Hat Virtualization 4 for Red Hat Enterprise Linux 8	`python-paramiko-0:2.4.3-3.el8ev`	RHSA-2022:4712

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2022-24302 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works