Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2018-1000805 — paramiko

HIGH

CVE-2018-1000805 is a high-severity (CVSS 8.8) CWE-863 vulnerability in paramiko. 1 public exploit reference exists, so weaponization risk is real. A fix is available for paramiko — see the affected versions and patch details below.

Paramiko Authentication Bypass vulnerability

Also known asGHSA-f2j6-wrhh-v25mPYSEC-2018-69
Published
Oct 8, 2018
Updated
Aug 7, 2026
Affected
5 pkgs
Patched
5 / 5
Exploits
1 known
Exploitation data as of Sep 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
4.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2018-1000805 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

5 pkgs affected
🐍paramiko🐍paramiko🐍paramiko🐍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

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 network connectivity.

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIparamiko≥ 2.4.0&&< 2.4.22.4.2pip install --upgrade 'paramiko==2.4.2'
🐍PyPIparamiko≥ 2.3.0&&< 2.3.32.3.3pip install --upgrade 'paramiko==2.3.3'
🐍PyPIparamiko≥ 2.2.0&&< 2.2.42.2.4pip install --upgrade 'paramiko==2.2.4'
🐍PyPIparamiko≥ 2.1.0&&< 2.1.62.1.6pip install --upgrade 'paramiko==2.1.6'
🐍PyPIparamiko≥ 1.5.1&&< 2.0.92.0.9pip install --upgrade 'paramiko==2.0.9'
Exploits & PoCs
1

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

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

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

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2018-1000805 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2018-1000805. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 HatCritical

This flaw is a user authentication bypass in the SSH Server functionality of paramiko (normally used by subclassing `paramiko.ServerInterface`). Where paramiko is used only for its client-side functionality (e.g. `paramiko.SSHClient`), the vulnerability is not exposed and thus cannot be exploited. The following Red…

ProductFixed inAdvisory
Red Hat Enterprise Linux 6python-paramiko-0:1.7.5-5.el6_10RHSA-2018:3406
Red Hat Enterprise Linux 7python-paramiko-0:2.1.1-9.el7RHSA-2018:3347
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7rhvm-appliance-0:4.2-20181026.1.el7RHBA-2018:3497
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7imgbased-0:1.0.29-1.el7evRHSA-2018:3470

Frequently Asked Questions

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 network connectivity.
O3 Security · Impact-Aware SCA

Is CVE-2018-1000805 in your dependencies?

O3 Security finds CVE-2018-1000805 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2018-1000805: paramiko RCE (High 8.8) | O3 Security