CVE-2025-26466: Openssh: denial-of-service in openssh
A flaw was found in the OpenSSH package. For each ping packet the SSH server receives, a pong packet is allocated in a memory buffer and stored in a queue of packages. It is only freed when the server/client key exchange has finished. A malicious client may keep sending such packages, leading to an uncontrolled increase in memory consumption on the server side. Consequently, the server may become unavailable, resulting in a denial of service attack.
Security readout for executives and security teams
Plain-English summary
CVE-2025-26466 is a denial-of-service flaw in OpenSSH where unauthenticated SSH traffic can make sshd retain growing memory during key exchange. The stated impact is service unavailability, not data theft or code execution. The bundle does not show active exploitation or name a fixed version.
Executive priority
Treat as a moderate availability risk. It is most urgent where SSH is internet-facing or critical to operations. Do not frame it as a breach-risk vulnerability based on the provided evidence; focus on service resilience, vendor status, and patch tracking.
Technical view
The issue is CWE-770: uncontrolled resource allocation. For each SSH ping packet, sshd allocates a pong packet into a queue that is freed only after server/client key exchange completes. A malicious client can keep sending packets, increasing server memory until availability is affected. CVSS is 5.9, network reachable, high attack complexity, no privileges required.
Likely exposure
Exposure is most relevant for systems running affected OpenSSH, especially internet-facing SSH servers. The bundle specifically names OpenSSH 9.5p1 and lists several Red Hat products as unaffected. Distribution-specific status should be checked against each vendor advisory because the bundle does not fully enumerate all fixed or affected package versions.
Exploitation context
The source bundle says KEV is false and provides no cited evidence of active exploitation. The described attack targets availability by exhausting memory during SSH negotiation. It requires network access to the SSH service but is assessed as high complexity in CVSS.
Researcher notes
Evidence supports a pre-authentication memory-consumption DoS in OpenSSH ping/pong handling during key exchange. The bundle lacks a named fixed version and does not prove exploitation in the wild. Validate exposure by package lineage and vendor backport status, not only upstream version strings.
Mitigation direction
Check OS and OpenSSH vendor advisories for fixed packages or backports.
Prioritize remediation for internet-exposed SSH services.
Reduce SSH exposure using VPNs, bastions, or allowlisted management networks.
Monitor sshd memory use, failed handshakes, and connection spikes.
Confirm Red Hat systems against Red Hat’s unaffected status before taking emergency action.
Validation and detection
Inventory OpenSSH versions and package build sources across servers.
Compare each platform against vendor advisories for CVE-2025-26466.
Identify externally reachable SSH services and management interfaces.
Review monitoring for abnormal sshd memory growth or connection churn.
Document any vendor status that is unknown or not yet assessed.
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-770: 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-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.