Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2016-0739

libssh: bits/bytes confusion resulting in truncated Difffie-Hellman secret length

Overview

Published
13 Apr 2016
Modified
6 May 2026
Medium CVE
0 Registry packages
3 OS packages
4 Linux distributions
Yes Fix available

Description

libssh before 0.7.3 improperly truncates ephemeral secrets generated for the (1) diffie-hellman-group1 and (2) diffie-hellman-group14 key exchange methods to 128 bits, which makes it easier for man-in-the-middle attackers to decrypt or intercept SSH sessions via unspecified vectors, aka a "bits/bytes confusion bug."

Source: OX vulnerability database

Severity

5.9 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Weakness: CWE-200

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 8 fixes

Red Hat 1 release · 1 package

fixed 1
libssh
Red Hat fixes for CVE-2016-0739
ReleasePackageFixed inAdvisory
7 libssh +1 0:0.7.1-2.el7 RHSA-2016:0566

debian 4 releases · 1 package

fixed 4
libssh
debian fixes for CVE-2016-0739
ReleasePackageFixed in
11 libssh 0.6.3-4.3
12 libssh 0.6.3-4.3
13 libssh 0.6.3-4.3
14 libssh 0.6.3-4.3

echo 1 release · 1 package

fixed 1
libssh
echo fixes for CVE-2016-0739
ReleasePackageFixed in
libssh 0.6.3-4.3

root.io debian 2 releases · 1 package

fixed 2
rootio-libssh
root.io debian fixes for CVE-2016-0739
ReleasePackageFixed in
11 rootio-libssh 0.6.3-4.3
12 rootio-libssh 0.6.3-4.3

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.