LiveActive security incident?Get immediate response
CVE Record

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.

LowCVSS 3.1Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

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.
Prepared
Confidence
high
Sources
6

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.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-8277 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
5Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
3.1CVSS 3.1LowCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L1.61.4redhat

Vulnerability scoring details

Base CVSS 3.1 score

3.1Low
CVSS 3.1 vector shape for CVE-2025-8277Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineredhat

    Reported to Red Hat.

  2. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  3. Source timelineredhat

    Made public.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorlibsshlibssh, 0.6.0unaffected
Red HatRed Hat Enterprise Linux 9libssh, 0:0.10.4-18.el9affected
Red HatRed Hat Enterprise Linux 9libssh, 0:0.10.4-18.el9affected
Red HatRed Hat Enterprise Linux 10libsshaffected
Red HatRed Hat Enterprise Linux 6libssh2unknown
Red HatRed Hat Enterprise Linux 7libssh2affected
Red HatRed Hat Enterprise Linux 8libsshaffected
Red HatRed Hat In-Vehicle Operating System 1libsshaffected
Red HatRed Hat OpenShift Container Platform 4rhcosaffected
Weakness

CWE details

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.