How severe is CVE-2018-7750?

CVE-2018-7750 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-7750?

CVE-2018-7750 affects the following packages: paramiko (PyPI), paramiko (PyPI), paramiko (PyPI), paramiko (PyPI), paramiko (PyPI), paramiko (PyPI), paramiko (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2018-7750?

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

How do I detect CVE-2018-7750 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-2018-7750 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2018-7750 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2018-7750, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations 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-2018-7750?

CVE-2018-7750 has an EPSS (Exploit Prediction Scoring System) score of 27.1%, placing it in the 98th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2018-7750?

CVE-2018-7750 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2018-7750 published, and has it been updated?

CVE-2018-7750 was published on March 13, 2018 and was last updated on October 24, 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

CRITICAL severity

CVE-2018-7750 — paramiko

CRITICALFix: paramiko/paramiko@fa29bd8

CVE-2018-7750 is a critical-severity (CVSS 9.8) Improper Authentication vulnerability in paramiko. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for paramiko — see the affected versions and patch details below.

Paramiko not properly checking authentication before processing other requests

Also known asGHSA-232r-66cg-79pxPYSEC-2018-19

Published

Mar 13, 2018

Updated

Oct 24, 2026

Affected

7 pkgs

Patched

7 / 7

Exploits

4 known

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

EPSS Exploitation Probability

via FIRST.org ↗

27.1%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% 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

7 pkgs affected

🐍paramiko🐍paramiko🐍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

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 does not properly check whether authentication is completed before processing other requests, as demonstrated by channel-open. A customized SSH client can simply skip the authentication step.

Affected Packages

7 total 7 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`paramiko`	≥ 2.0.0&&< 2.0.8	2.0.8`pip install --upgrade 'paramiko==2.0.8'`
🐍PyPI	`paramiko`	≥ 2.1.0&&< 2.1.5	2.1.5`pip install --upgrade 'paramiko==2.1.5'`
🐍PyPI	`paramiko`	≥ 2.2.0&&< 2.2.3	2.2.3`pip install --upgrade 'paramiko==2.2.3'`
🐍PyPI	`paramiko`	≥ 2.3.0&&< 2.3.2	2.3.2`pip install --upgrade 'paramiko==2.3.2'`
🐍PyPI	`paramiko`	≥ 2.4.0&&< 2.4.1	2.4.1`pip install --upgrade 'paramiko==2.4.1'`
🐍PyPI	`paramiko`	≥ 1.18.0&&< 1.18.5	1.18.5`pip install --upgrade 'paramiko==1.18.5'`

Affected Products

11 products · 23 configurations

debian linuxdebian

2 versions

8.09.0

Application

paramikoparamiko

≥ 2.3.0 && < 2.3.2

1 version

2.4.0

Application

ansible engineredhat

2 versions

2.02.4

Application

cloudformsredhat

2 versions

4.54.6

enterprise linux desktopredhat

1 version

6.0

enterprise linux serverredhat

2 versions

6.07.0

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.

EDB-45712remotelinux

Paramiko 2.4.1 - Authentication Bypass

by Adam Brown · Oct 29, 2018

Exploit-DB Source

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.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-7750 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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…

Product	Fixed in	Advisory
CloudForms Management Engine 5.8	`ansible-0:2.4.4.0-1.el7ae`	RHSA-2018:1972
CloudForms Management Engine 5.9	`ansible-0:2.4.4.0-1.el7ae`	RHSA-2018:1328
Red Hat Ansible Engine 2.4 for RHEL 7	`python-paramiko-0:2.1.1-4.el7`	RHSA-2018:1213
Red Hat Ansible Engine 2 for RHEL 7	`python-paramiko-0:2.1.1-4.el7`	RHSA-2018:0646
Red Hat Enterprise Linux 6	`python-paramiko-0:1.7.5-4.el6_9`	RHSA-2018:1124
Red Hat Enterprise Linux 6.4 Advanced Update Support	`python-paramiko-0:1.7.5-4.el6_4`	RHSA-2018:1125
Red Hat Enterprise Linux 7 Extras	`python-paramiko-0:2.1.1-4.el7`	RHSA-2018:0591
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7	`python-paramiko-0:2.1.1-4.el7`	RHSA-2018:1274

UbuntuCRITICAL

USN-3603-2Ubuntu USN-3603-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-7750 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2018-7750 — paramiko

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2018-7750 in your dependencies?