CVE-2025-8277: Libssh: memory exhaustion via repeated key exchange in libssh
A flaw was found in libssh's handling of key exchange (KEX) processes when a client repeatedly sends incorrect KEX guesses. The library fails to free memory during these rekey operations, which can gradually exhaust system memory. This issue can lead to crashes on the client side, particularly when using libgcrypt, which impacts application stability and availability.
Security readout for executives and security teams
Plain-English summary
CVE-2025-8277 is a low-severity libssh memory leak during SSH key exchange. Repeated bad key-exchange guesses can consume memory over time and may crash affected client-side applications, reducing availability. There is no provided evidence of active exploitation or KEV listing.
Executive priority
Treat as routine patch management, not an emergency, unless critical services rely heavily on affected libssh clients. Prioritize systems where client crashes would disrupt automation, operations, or customer-facing workflows.
Technical view
libssh does not free memory correctly during repeated rekey operations triggered by incorrect KEX guesses. The issue is CWE-401 with CVSS 3.1 score 3.1: network reachable, high complexity, low privileges required, no confidentiality or integrity impact, and low availability impact.
Likely exposure
Exposure is most relevant where applications use affected libssh packages in listed Red Hat products: RHEL 8, 9, 10, RHIVOS 1, OpenShift Container Platform 4 rhcos, and RHEL 7 libssh2 per the bundle. RHEL 6 libssh2 status is listed as unknown.
Exploitation context
Sources describe memory exhaustion through repeated incorrect KEX guesses during SSH rekeying. The reported impact is client-side crashes, especially with libgcrypt. The CVSS vector indicates network access, high attack complexity, low privileges, no user interaction, and limited availability impact.
Researcher notes
No KEV listing is provided, and the bundle does not show active exploitation. Patch details beyond the Red Hat errata and libssh advisory URLs are not included here. Validate exact affected and fixed versions from vendor advisories before making remediation decisions.
Mitigation direction
Apply vendor updates from RHSA-2026:18683 where applicable.
Follow libssh and operating-system vendor guidance for fixed package versions.
Limit SSH interactions with untrusted endpoints where operationally feasible.
Monitor affected applications for memory growth and crashes.
Validation and detection
Inventory libssh and libssh2 packages across affected platforms.
Identify applications dynamically or statically linked to libssh.
Check Red Hat CVE status for each product version.
Confirm RHSA-2026:18683 or later relevant updates are installed.
Review logs for crashes around SSH key exchange or rekey events.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.