GHSA-f2j6-wrhh-v25m
HIGHGHSA-f2j6-wrhh-v25m is a high-severity (CVSS 8.8) CWE-863 vulnerability in paramiko. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-f2j6-wrhh-v25m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Paramiko Authentication Bypass vulnerability
Blast Radius
paramiko🐍paramiko🐍paramiko🐍paramiko🐍paramikoReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | paramiko | ≥ 2.4.0&&< 2.4.2 | 2.4.2 |
| 🐍PyPI | paramiko | ≥ 2.3.0&&< 2.3.3 | 2.3.3 |
| 🐍PyPI | paramiko | ≥ 2.2.0&&< 2.2.4 | 2.2.4 |
| 🐍PyPI | paramiko | ≥ 2.1.0&&< 2.1.6 | 2.1.6 |
| 🐍PyPI | paramiko | ≥ 1.5.1&&< 2.0.9 | 2.0.9 |
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 dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for paramiko. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update paramiko to 2.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f2j6-wrhh-v25m is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-f2j6-wrhh-v25m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-f2j6-wrhh-v25m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-f2j6-wrhh-v25m in your dependencies?
O3 detects GHSA-f2j6-wrhh-v25m across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.