GHSA-wqmm-q65g-2hqr — paramiko
MEDIUMGHSA-wqmm-q65g-2hqr is a medium-severity (CVSS 6.5) 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 Unsafe randomness usage may allow access to sensitive information
EPSS Exploitation Probability
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
GHSA-wqmm-q65g-2hqr 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 377,636 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
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
common.py in Paramiko 1.7.1 and earlier, when using threads or forked processes, does not properly use RandomPool, which allows one session to obtain sensitive information from another session by predicting the state of the pool.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | paramiko | all versions | 1.7.1-3pip install --upgrade 'paramiko==1.7.1-3' |
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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update paramiko to 1.7.1-3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wqmm-q65g-2hqr 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-wqmm-q65g-2hqr can be triaged on real exposure rather than presence alone.
Tailored to GHSA-wqmm-q65g-2hqr. 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-wqmm-q65g-2hqr in your dependencies?
O3 Security finds GHSA-wqmm-q65g-2hqr across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.