# libssh-gcrypt-4 0.10.6-2ubuntu0.1: libssh-gcrypt-4 0.10.6-2ubuntu0.1 for Ubuntu 24.04.5 LTS (noble)

libssh-gcrypt-4 0.10.6-2ubuntu0.1, released June 24, 2025, fixes 6 CVEs in libssh-gcrypt-4. None of them is reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/fix/linux/ubuntu-noble-libssh-gcrypt-4-0.10.6-2ubuntu0.1
- Platform: Linux
- Released: Jun 24, 2025
- Priority: High (Closes CVE-2025-5987, high severity)
- CVEs: 6, exploited: 0, on CISA KEV: 0

## Applies to

| Product | Release | Fixed in |
|---|---|---|
| [libssh-gcrypt-4](https://patchblox.com/security/data/product/linux/libssh-gcrypt-4.md) | Ubuntu 24.04.5 LTS (noble) | 0.10.6-2ubuntu0.1 |

## CVEs this fix closes

| CVE | Priority | Title | CVSS | EPSS | Exploitation |
|---|---|---|---:|---:|---|
| [CVE-2025-5987](https://patchblox.com/security/data/cve/CVE-2025-5987.md) | High | Libssh: invalid return code for chacha20 poly1305 with openssl backend | 8.1 | 0.0173 |  |
| [CVE-2025-5372](https://patchblox.com/security/data/cve/CVE-2025-5372.md) | High | Libssh: incorrect return code handling in ssh_kdf() in libssh | 8.8 | 0.0051 |  |
| [CVE-2025-5318](https://patchblox.com/security/data/cve/CVE-2025-5318.md) | Routine | Libssh: out-of-bounds read in sftp_handle() | 5.4 | 0.0189 |  |
| [CVE-2025-5351](https://patchblox.com/security/data/cve/CVE-2025-5351.md) | Routine | Libssh: double free vulnerability in libssh key export functions | 6.5 | 0.0063 |  |
| [CVE-2025-4878](https://patchblox.com/security/data/cve/CVE-2025-4878.md) | Routine | Libssh: use of uninitialized variable in privatekey_from_file() | 6.5 | 0.0023 |  |
| [CVE-2025-4877](https://patchblox.com/security/data/cve/CVE-2025-4877.md) | Routine | Libssh: write beyond bounds in binary to base64 conversion functions | 6.5 | 0.0022 |  |

---

Data as of 2026-11-12T19:57:06Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.