Quick answers
- Is CVE-2025-5372 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-5372 being exploited in the wild.
- How severe is CVE-2025-5372?
- Medium severity, with a CVSS score of 5, published 4 July 2025.
- Which products and versions are affected?
- Libssh < 0.11.2.
- Is there a fix for CVE-2025-5372?
- A patch was published on 2025-11-24: Red Hat released initial patches for RHEL 8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-5372 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-5372?
- Check whether you run Libssh at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A flaw exists in the ssh_kdf() function of libssh when compiled against OpenSSL versions older than 3.0. The vulnerability stems from an inconsistent interpretation of return values: OpenSSL uses 0 to signal a failure, whereas libssh interprets 0 as success. Consequently, if the key derivation function fails, libssh may proceed using uninitialized cryptographic key buffers. This can be exploited by a network-based attacker to compromise the confidentiality, integrity, and availability of SSH sessions. The issue is addressed in libssh version 0.11.2 and various Red Hat package updates.
Affected products
- libssh libssh < 0.11.2
- Red Hat Enterprise Linux 6.0, 7.0, 8.0, 9.0, 10.0
- Red Hat OpenShift Container Platform 4.0
Timeline
- 2025-07-04: disclosed
- 2025-07-04: advisory
- 2025-11-24: patched: Red Hat released initial patches for RHEL 8