Vulnerabilities

Vulnerability · CVE-2016-6210

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, whic…

Published Feb 13, 2017 · catalog updated Jun 17, 2026 · the affected product

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check this week

CVE-2016-6210 is not in CISA KEV. FIRST estimates a 88.94% chance of exploitation in the next 30 days. Check whether you run the affected product.

Gaps on this record

  • No plain product name is stored. The page cannot tell you which product to check.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium5.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
88.94%
Remediation
Version ranges on file
Affected products
cpe openbsd/openssh

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe openbsd/openssh<= 7.2

How to fix CVE-2016-6210

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2016-6210 is not in CISA KEV. FIRST estimates a 88.94% chance of exploitation in the next 30 days. Check whether you run the affected product.

Which versions are affected?

Compare what you have installed with <= 7.2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-200: Exposure of Sensitive Information. EPSS 88.94%. There is no CISA KEV listing. A public exploit reference is linked in Sources. That is not the same as confirmed exploitation. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Feb 13, 2017 · Monitored products — critical

    Detected

    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.

  2. Jun 17, 2026 · Monitored products — critical

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2016-6210

    Official CVE identifier

    cve.org
  • Monitored products — criticalVendor advisoryCVE-2016-6210

    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.

    nvd.nist.gov
  • Metasploit ModulesPublic exploit moduleauxiliary_scanner/ssh/ssh_enumusers

    Public module reference (normal). Module source is not copied into this catalog.

    rapid7.com

References

Freshness

Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Metasploit ModulesNov 7, 2026
  • CVE.orgNov 4, 2026
  • Monitored products — criticalNov 4, 2026