CVE-2016-6210

CRITICALNVD 5.99.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 89% probability of exploitation within the next 30 days (top 0.2% of all CVEs). NVD baseline CVSS 5.9 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 1,750 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 89%
  • Public exploit code is available (Metasploit, ssvc poc, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 89%CVSS: 5.9Exploit: Metasploit · ssvc poc · epss top5pct · epss high · public exploitExposed: 1,750

A fix is available — apply it.

sshd in OpenSSH before 7.3, when SHA256 or SHA512 are used for user password hashing, uses BLOWFISH hashing on a static password when the username does not exist, which allows remote attackers to enumerate users by leveraging the timing difference between responses when a large password is provided.

Live · internet exposure

1,750 internet-exposed hosts are running an affected version of CVE-2016-6210 right now.

across 38 countries (China, United States, Germany, France, Singapore)top: openssh
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
5.9
EG Score
9.0(high)
EG Risk
76(Track)
EG Risk 76/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation89% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
89%
EPSS %ILE
100%
KEV
Not listed

Published

February 13, 2017

Last Modified

June 17, 2026

References (24)

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntussh-krb5 (1:7.2p2-4ubuntu2.1) @ xenial2026-05-22ubuntu
redhatopenssh-0:5.3p1-123.el6_92017-08-31redhat
redhatopenssh-0:7.4p1-11.el72017-08-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 9 ecosystems)
Alpine:v3.2(1)
PackageVulnerable rangeFixed inDependents
openssh5.1_p1-r1 ... 6.8_p1-r6 (52 versions)6.8_p1-r7—
Alpine:v3.3(1)
PackageVulnerable rangeFixed inDependents
openssh5.1_p1-r1 ... 7.2_p2-r0 (59 versions)7.2_p2-r1—
Alpine:v3.4(1)
PackageVulnerable rangeFixed inDependents
openssh5.1_p1-r1 ... 7.2_p2-r0 (59 versions)7.2_p2-r1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
openssh—1:7.2p2-6—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssh—1:7.2p2-6—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssh—1:7.2p2-6—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssh—1:7.2p2-6—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
openssh1:6.0p1-4, 1:6.0p1-4+deb7u1, 1:6.0p1-4+deb7u2, 1:6.0p1-4+deb7u3, 1:6.0p1-4+deb7u41:6.0p1-4+deb7u5—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
openssh1:6.7p1-5, 1:6.7p1-5+deb8u1, 1:6.7p1-5+deb8u21:6.7p1-5+deb8u3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 3× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 13:59 UTCEPSS rescore
  2. 2026-09-18 19:22 UTCEPSS rescore
  3. 2026-09-18 15:50 UTCOSV refresh
  4. 2026-09-11 14:46 UTCEPSS rescore
  5. 2026-09-10 09:26 UTCEPSS rescore
  6. 2026-09-04 13:56 UTCEPSS rescore
  7. 2026-08-30 19:37 UTCOSV refresh
  8. 2026-08-28 21:35 UTCEPSS rescore
  9. 2026-08-27 14:20 UTCEPSS rescore
  10. 2026-08-25 13:44 UTCEPSS rescore
  11. 2026-08-21 23:44 UTCEPSS rescore
  12. 2026-08-14 05:59 UTCOSV refresh
  13. 2026-08-12 13:46 UTCEPSS rescore
  14. 2026-08-08 16:32 UTCEPSS rescore
  15. 2026-08-07 16:22 UTCEPSS rescore
  16. 2026-07-30 01:26 UTCEPSS rescore
  17. 2026-07-30 01:26 UTCEPSS rescore
  18. 2026-07-29 12:07 UTCOSV refresh
  19. 2026-07-28 15:31 UTCEPSS rescore
  20. 2026-07-24 14:13 UTCEPSS rescore
  21. 2026-07-23 01:23 UTCEG score recompute
  22. 2026-07-22 22:03 UTCEG score recompute
  23. 2026-07-22 14:04 UTCEPSS rescore
  24. 2026-07-19 02:26 UTCEPSS rescore
  25. 2026-07-19 02:26 UTCEPSS rescore
Show 40 more
  1. 2026-07-18 10:00 UTCEPSS rescore
  2. 2026-07-18 10:00 UTCEPSS rescore
  3. 2026-07-15 16:54 UTCEPSS rescore
  4. 2026-07-15 16:54 UTCEPSS rescore
  5. 2026-07-12 05:43 UTCEPSS rescore
  6. 2026-07-12 05:43 UTCEPSS rescore
  7. 2026-07-12 03:41 UTCOSV refresh
  8. 2026-07-11 08:24 UTCEPSS rescore
  9. 2026-07-09 19:06 UTCEPSS rescore
  10. 2026-06-28 04:53 UTCEPSS rescore
  11. 2026-06-25 13:47 UTCEPSS rescore
  12. 2026-06-24 14:02 UTCEPSS rescore
  13. 2026-06-23 21:30 UTCEPSS rescore
  14. 2026-06-23 10:00 UTCOSV refresh
  15. 2026-06-15 17:45 UTCEPSS rescore
  16. 2026-06-12 23:09 UTCEPSS rescore
  17. 2026-06-08 14:14 UTCEPSS rescore
  18. 2026-06-07 15:22 UTCEPSS rescore
  19. 2026-06-07 15:22 UTCEPSS rescore
  20. 2026-06-06 13:45 UTCEPSS rescore
  21. 2026-06-06 13:45 UTCEPSS rescore
  22. 2026-06-06 10:21 UTCOSV refresh
  23. 2026-06-05 22:44 UTCEPSS rescore
  24. 2026-06-05 06:08 UTCEPSS rescore
  25. 2026-06-05 06:08 UTCEPSS rescore
  26. 2026-06-04 13:10 UTCEPSS rescore
  27. 2026-06-04 13:10 UTCEPSS rescore
  28. 2026-06-02 20:10 UTCEPSS rescore
  29. 2026-05-29 13:41 UTCEPSS rescore
  30. 2026-05-28 13:42 UTCEPSS rescore
  31. 2026-05-28 13:42 UTCEPSS rescore
  32. 2026-05-22 16:19 UTCEG score recompute
  33. 2026-05-22 16:19 UTCVendor advisory
  34. 2026-05-22 16:18 UTCGHSA enrichment
  35. 2026-05-20 22:37 UTCEPSS rescore
  36. 2026-05-20 22:37 UTCEPSS rescore
  37. 2026-05-20 22:37 UTCEPSS rescore
  38. 2026-05-18 21:30 UTCEPSS rescore
  39. 2026-05-18 21:30 UTCEPSS rescore
  40. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(5 references)

Working exploit code is in the public domain (1 Metasploit module) (2 GitHub PoCs) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCserexp/poc-CVE20166210
    First seen May 2, 2026

    CVE-2016-6210/Openssh 7.2p2 side channel info disclosure POC

    Open source ↗
  • GitHub PoCjustlce/CVE-2016-6210-Exploit
    First seen Aug 25, 2019

    OpenSSH Username Enumeration - CVE-2016-6210

    Open source ↗
  • Exploit-DBEDB-40136
    First seen Jul 20, 2016

    OpenSSH 7.2p2 - Username Enumeration

    Open source ↗
  • Exploit-DBEDB-40113
    First seen Jul 18, 2016

    OpenSSHd 7.2p2 - Username Enumeration

    Open source ↗
  • Metasploitauxiliary/scanner/ssh/ssh_enumusers✓ verified
    First seen Jan 1, 2016

    SSH Username Enumeration

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2016-6210?
CVE-2016-6210 is a critical vulnerability published on February 13, 2017. sshd in OpenSSH before 7.3, when SHA256 or SHA512 are used for user password hashing, uses BLOWFISH hashing on a static password when the username does not exist, which allows remote attackers to enumerate users by leveraging the timing difference between responses when a large password is provided.
When was CVE-2016-6210 disclosed?
CVE-2016-6210 was first published in the National Vulnerability Database on February 13, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-6210 actively exploited?
CVE-2016-6210 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 89% probability of exploitation in the next 30 days, which ranks it in the top 0.2% of all scored CVEs.
What is the CVSS score of CVE-2016-6210?
CVE-2016-6210 has a CVSS v3 base score of 5.9 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2016-6210?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-6210, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-6210

Explore →

Is Your Infrastructure Affected by CVE-2016-6210?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs