# CVE-2018-7750: Paramiko not properly checking authentication before processing other requests

> Attackers can bypass SSH authentication in Paramiko by skipping the auth step, allowing unauthorized access to the server.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2018-7750, DEBIAN-CVE-2018-7750, GHSA-232r-66cg-79px, MGASA-2018-0204, PYSEC-2018-19, RHSA-2018:0591, RHSA-2018:0646, RHSA-2018:1124, RHSA-2018:1125, RHSA-2018:1213, RHSA-2018:1274, SUSE-SU-2018:0844-1, SUSE-SU-2018:0873-1, SUSE-SU-2018:1850-1, SUSE-SU-2018:1971-1, SUSE-SU-2018:2777-1, UBUNTU-CVE-2018-7750, USN-3603-1

## What is CVE-2018-7750?

CVE-2018-7750 is a critical authentication bypass vulnerability in Debian Debian Linux, published on 13 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-7750?

15 open source packages ship an affected version, including paramiko. It affects 11 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `paramiko` | PyPI | All versions | 1.17.6, 1.18.5, 2.0.8, 2.1.5, 2.2.3, 2.3.2 |
| `paramiko` | PyPI | All versions | 1.17.6 |
| `paramiko` | PyPI | All versions | 1.17.6 |
| `paramiko` | PyPI | From 1.18.0 | 1.18.5 |
| `paramiko` | PyPI | From 1.18.0 | 1.18.5 |
| `paramiko` | PyPI | From 2.0.0 | 2.0.8 |
| `paramiko` | PyPI | From 2.0.0 | 2.0.8 |
| `paramiko` | PyPI | From 2.1.0 | 2.1.5 |
| `paramiko` | PyPI | From 2.1.0 | 2.1.5 |
| `paramiko` | PyPI | From 2.2.0 | 2.2.3 |
| `paramiko` | PyPI | From 2.2.0 | 2.2.3 |
| `paramiko` | PyPI | From 2.3.0 | 2.3.2 |
| `paramiko` | PyPI | From 2.3.0 | 2.3.2 |
| `paramiko` | PyPI | From 2.4.0 | 2.4.1 |
| `paramiko` | PyPI | From 2.4.0 | 2.4.1 |
| `python-paramiko` | Red Hat:ansible_engine:2.4::el7 | All versions | 0:2.1.1-4.el7 |
| `python-paramiko` | Red Hat:ansible_engine:2::el7 | All versions | 0:2.1.1-4.el7 |
| `python-paramiko` | Red Hat:enterprise_linux:6::client | All versions | 0:1.7.5-4.el6_9 |
| `python-paramiko` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.7.5-4.el6_9 |
| `python-paramiko` | Red Hat:enterprise_linux:6::server | All versions | 0:1.7.5-4.el6_9 |
| `python-paramiko` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.7.5-4.el6_9 |
| `python-paramiko` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:2.1.1-4.el7 |
| `python-paramiko-doc` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:2.1.1-4.el7 |
| `python-paramiko` | Red Hat:rhel_aus:6.4::server | All versions | 0:1.7.5-4.el6_4 |
| `python-paramiko` | Red Hat:rhel_aus:6.5::server | All versions | 0:1.7.5-4.el6_5 |
| `python-paramiko` | Red Hat:rhel_aus:6.6::server | All versions | 0:1.7.5-4.el6_6 |
| `python-paramiko` | Red Hat:rhel_eus:6.7::computenode | All versions | 0:1.7.5-4.el6_7 |
| `python-paramiko` | Red Hat:rhel_eus:6.7::server | All versions | 0:1.7.5-4.el6_7 |
| `python-paramiko` | Red Hat:rhel_extras_other:7 | All versions | 0:2.1.1-4.el7 |
| `python-paramiko-doc` | Red Hat:rhel_extras_other:7 | All versions | 0:2.1.1-4.el7 |
| `python-paramiko` | Red Hat:rhel_tus:6.6::server | All versions | 0:1.7.5-4.el6_6 |
| `python-paramiko` | Red Hat:rhev_manager:4 | All versions | 0:2.1.1-4.el7 |
| `python-paramiko-doc` | Red Hat:rhev_manager:4 | All versions | 0:2.1.1-4.el7 |
| `python-paramiko` | SUSE:Enterprise Storage 3 | All versions | 1.15.2-2.6.1 |
| `python-paramiko` | SUSE:Enterprise Storage 4 | All versions | 2.0.8-3.3.1 |
| `python-paramiko` | SUSE:Enterprise Storage 5 | All versions | 2.0.8-3.3.1 |
| `python-paramiko` | SUSE:Linux Enterprise Module for Public Cloud 12 | All versions | 1.15.2-2.9.1 |
| `python-paramiko` | SUSE:Linux Enterprise Module for Public Cloud 12 | All versions | 1.18.5-2.12.1 |
| `python-paramiko` | SUSE:OpenStack Cloud 6 | All versions | 1.15.2-2.6.1 |
| `python-paramiko` | SUSE:OpenStack Cloud 7 | All versions | 2.0.8-3.3.1 |

Products: Debian Debian Linux, Paramiko Paramiko, Redhat Ansible Engine, Redhat Cloudforms, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation, Redhat Virtualization.

## How do I fix CVE-2018-7750?

Upgrade paramiko to a fixed version for your release line: 1.17.6, 1.18.5, 2.0.8 or 2.1.5.

## Is CVE-2018-7750 being exploited?

There is no known exploitation of CVE-2018-7750 in the wild and no public exploit code.

Public exploit code:

- an RCE (remote command execution) approach of CVE-2018-7750 (github_poc): https://github.com/jm33-m0/CVE-2018-7750
- Paramiko 2.4.1 - Authentication Bypass (exploitdb)
- https://github.com/tlavi00/CVE-2018-7750 (github_poc): https://github.com/tlavi00/CVE-2018-7750

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7750 and fix it if it is affected.

What it is: CVE-2018-7750 is a critical authentication bypass vulnerability in Debian Debian Linux, published on 13 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-7750 in the wild and no public exploit code.

Affected packages and fixed versions:
- paramiko (PyPI): affected all versions; fixed in 1.17.6, 1.18.5, 2.0.8, 2.1.5, 2.2.3, 2.3.2
- paramiko (PyPI): affected all versions; fixed in 1.17.6
- paramiko (PyPI): affected all versions; fixed in 1.17.6
- paramiko (PyPI): affected from 1.18.0; fixed in 1.18.5
- paramiko (PyPI): affected from 1.18.0; fixed in 1.18.5
- paramiko (PyPI): affected from 2.0.0; fixed in 2.0.8
- paramiko (PyPI): affected from 2.0.0; fixed in 2.0.8
- paramiko (PyPI): affected from 2.1.0; fixed in 2.1.5
- paramiko (PyPI): affected from 2.1.0; fixed in 2.1.5
- paramiko (PyPI): affected from 2.2.0; fixed in 2.2.3
- paramiko (PyPI): affected from 2.2.0; fixed in 2.2.3
- paramiko (PyPI): affected from 2.3.0; fixed in 2.3.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-7750/ (Markdown: https://insights.sbomify.com/CVE-2018-7750/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-7750
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-7750
- OSV: https://osv.dev/vulnerability/CVE-2018-7750

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-7750/
Summaries are generated and may contain mistakes; the official description above is the record.
