CVE-2025-26466 is a pre-authentication denial of service in OpenSSH 9.5p1 to 9.9p1. A client that keeps sending SSH2_MSG_PING packets during the key exchange makes sshd queue PONG replies in memory and then spend quadratic CPU time flushing them. NVD scores it 5.9. Fixed in OpenSSH 9.9p2; PerSourcePenalties, MaxStartups and LoginGraceTime limit it.
Vulnerability summary
CVSS base score
5.9
Medium severity
EPSS score (FIRST)
38.7%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2025-26466 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| OpenSSH (sshd, also the ssh client per Qualys) | cpe:2.3:a:openbsd:openssh:*:*:*:*:*:*:*:* | 9.5p1 to 9.9p1 inclusive (OpenSSH security page); NVD CPEs 9.5p1 through 9.9p1; fixed in 9.9p2 |
| Debian openssh package | pkg:deb/debian/openssh | bullseye and bookworm not affected (vulnerable code introduced later); fixed in 1:9.9p2-1 (unstable) (Debian security tracker) |
| Red Hat Enterprise Linux openssh | pkg:rpm/redhat/openssh | Fixed in openssh-8.7p1-45.el9 (RHEL 9) and openssh-9.9p1-7.el10_0 (RHEL 10); RHEL 8 and older not affected (Red Hat) |
| Buildroot package/openssh | — | Bumped to 9.9p2 on 2025-02-20 (commit 002931cc); fixed in 2025.02, 2024.11.2 and 2024.02.11; 2024.11.1 carries 9.9p1 and 2024.02.10 carries 9.7p1 |
| OpenWrt packages feed: openssh | — | openwrt-24.10 carries 9.9p2 (fixed); openwrt-23.05 and openwrt-22.03 carry 9.8p1 without a fix for this CVE; openwrt-21.02 carries 8.4p1, before the vulnerable code (OpenWrt packages repository, as of 2026-11-19) |
| Siemens SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP and SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (GNU/Linux subsystem) | — | V3.1.0 to before V3.1.5; update to V3.1.5 or later (Siemens SSA-398330) |
What does this mean for affected devices?
CVE-2025-26466 is a pre-authentication denial of service in OpenSSH: each SSH2_MSG_PING packet received during a key exchange makes the peer queue a PONG reply in memory that is only freed when the key exchange ends, so a client that keeps sending pings drives up memory and then CPU use. The weakness is CWE-770 (allocation of resources without limits or throttling); NVD lists CWE-770 as a Secondary entry, both its own and Red Hat's. NVD's Primary score is 5.9, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, the same score and vector that Red Hat, the CNA, published with a Moderate rating. NVD published the entry on 2025-02-28 (NVD, CVE record, Red Hat).
What has to be true for an attack to work?
The attacker only needs to reach the SSH port; no credentials are involved. The Qualys advisory, posted to oss-security at the coordinated release on 2025-02-18, explains that for every 16-byte PING the peer allocates a 256-byte PONG buffer that stays queued until the key exchange finishes, and that re-buffering the queued PONGs afterwards costs quadratic CPU time. Sending roughly 16 MB of PINGs and disconnecting left the server CPU at 100% for 2 minutes, the default LoginGraceTime. Because sshd accepts 100 concurrent unauthenticated connections by default, Qualys says MaxStartups and PerSourcePenalties are needed as well for a full mitigation. Qualys found the client side affected too, with no mitigation there, and used this bug as the memory-exhaustion step of its CVE-2025-26465 impersonation attack. On a small embedded device with little RAM, the practical effect is an SSH service, and possibly the device's management plane, starved of memory or CPU.
Which versions and devices are affected?
The OpenSSH 9.9p2 release notes and the OpenSSH security page list sshd(8) in OpenSSH 9.5p1 to 9.9p1 inclusive; Qualys traces the bug to commit dce6d80 ("Introduce a transport-level ping facility"), added in August 2023. Older code is not affected, so judge by the code, not the version string:
- Debian marks bullseye and bookworm not affected ("vulnerable code introduced later") and fixed unstable in 1:9.9p2-1 (Debian security tracker). NVD's CPE configuration still lists Debian 11 and 12.
- Red Hat lists RHEL 9 as affected even though its package is based on 8.7p1: RHEL 9 is fixed in openssh-8.7p1-45.el9 and RHEL 10 in openssh-9.9p1-7.el10_0, while RHEL 8 and older are not affected. A banner reading 8.7p1 on a RHEL 9 derived image can therefore still be vulnerable.
- Buildroot moved to 9.9p2 on 2025-02-20 (Buildroot commit 002931cc); 2025.02, 2024.11.2 and 2024.02.11 ship 9.9p2, while 2024.11.1 ships 9.9p1 and 2024.02.10 ships 9.7p1.
- In the OpenWrt packages feed, openwrt-24.10 moved to 9.9p2 on 2025-03-12 (OpenWrt commit f1bf549d). As of 2026-11-19, openwrt-23.05 and openwrt-22.03 carry 9.8p1 with no patch for this CVE (openwrt-23.05 Makefile); openwrt-21.02 carries 8.4p1, which predates the ping code.
Siemens ProductCERT SSA-398330 lists CVE-2025-26466 for the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518-4 PN/DP MFP and 1518F-4 PN/DP MFP and the SIPLUS S7-1500 CPU 1518-4 PN/DP MFP, V3.1.0 to before V3.1.5, and recommends updating to V3.1.5 or later. Siemens scores it 5.9 with CWE-400.
How do you fix CVE-2025-26466?
Update to OpenSSH 9.9p2 or later, or to a vendor package carrying the fix commit 6ce00f0. Until then, OpenSSH says the condition "may be mitigated using the existing PerSourcePenalties feature" (9.8p1 and later); Red Hat's mitigation sets reasonable MaxStartups, PerSourcePenalties and LoginGraceTime values together. Limiting SSH to a management network helps on devices where none of these can be changed. Our OpenSSH vulnerabilities in embedded firmware guide explains how to read the version, check backports and harden sshd_config. Builds in the 9.5p1 to 9.7p1 range also need the fix for regreSSHion, CVE-2024-6387, and musl builds without PAM before 10.6p2 need the fix for CVE-2026-123158.
Is CVE-2025-26466 exploited?
It is not in the CISA KEV catalog as of 2026-11-19 (catalog version 2026.11.18, 1,786 entries). CISA's SSVC entry, dated 2025-03-04, records exploitation as "poc", automatable as "no" and technical impact as "partial". FIRST EPSS gives it 0.387, the 98.6th percentile, in the 2026-11-18 dataset (CISA KEV, FIRST EPSS).
Evidence
- NVD: for each ping packet the SSH server receives, a pong packet is allocated and queued, only freed when the key exchange finishes; a malicious client may keep sending them, causing uncontrolled memory consumption and DoS. NVD Primary CVSS v3.1 5.9 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H; CWE-770 listed as Secondary by NVD and by Red Hat; CPEs openbsd:openssh 9.5p1 to 9.9p1, Ubuntu 24.04/24.10, Debian 11/12; published 2025-02-28. — NVD
- CVE.org: state PUBLISHED, CNA Red Hat, published 2025-02-28, CVSS 3.1 5.9 same vector, Red Hat severity Moderate, CWE-770; OpenSSH 9.5p1 to 9.9p1 affected; CISA-ADP SSVC (2025-03-04) exploitation poc, automatable no, technical impact partial; Siemens ADP lists SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.0 to before V3.1.5. — CVE.org
- OpenSSH 9.9p2 released 2025-02-18: fixes CVE-2025-26466, sshd(8) in 9.5p1 to 9.9p1 inclusive vulnerable to memory/CPU DoS related to SSH2_MSG_PING handling; may be mitigated using PerSourcePenalties. Security page lists the same range. — OpenSSH
- Qualys advisory: pre-authentication asymmetric memory and CPU DoS against client and server, introduced August 2023 by commit dce6d80; 16B PING yields 256B PONG buffer not freed until end of key exchange; re-buffering is O(n^2); ~16MB of PINGs leaves the server CPU at 100% for 2 minutes (default LoginGraceTime); 100 concurrent connections by default so MaxStartups and PerSourcePenalties are also needed; no client-side mitigation; coordinated release 2025-02-18. — Qualys / oss-security
- Debian: bullseye and bookworm not affected (vulnerable code introduced later); unstable fixed in 1:9.9p2-1; introduced by commit dce6d80 (V_9_5_P1), fixed by commit 6ce00f0. — Debian security tracker
- Red Hat: Moderate, 5.9; RHEL 8 and older not affected; fixed in openssh-0:8.7p1-45.el9 (RHEL 9) and openssh-0:9.9p1-7.el10_0 (RHEL 10); mitigation: set MaxStartups, PerSourcePenalties and LoginGraceTime, all three needed for full mitigation. — Red Hat
- Buildroot commit 002931cc (2025-02-20) 'package/openssh: security bump version to 9.9p2', fixes CVE-2025-26465 and CVE-2025-26466; openssh.mk is 9.9p2 in tags 2025.02, 2024.11.2 and 2024.02.11, 9.9p1 in 2024.11.1 and 9.7p1 in 2024.02.10. — Buildroot
- OpenWrt packages: commit f1bf549d (2025-03-12) bumps openwrt-24.10 to 9.9p2 citing CVE-2025-26465 and CVE-2025-26466; openwrt-23.05 (PKG_VERSION 9.8p1, patches 0001-avoid-password-authn-bypass and 900-sshd_config-include-dir) and openwrt-22.03 (9.8p1) carry no fix; openwrt-21.02 is 8.4p1 (read 2026-11-19). — OpenWrt packages
- Siemens SSA-398330 (V2.8, 2026-10-13): CVE-2025-26466 affects the additional GNU/Linux subsystem of SIMATIC S7-1500 CPU 1518-4 PN/DP MFP and 1518F-4 PN/DP MFP and SIPLUS S7-1500 CPU 1518-4 PN/DP MFP, V3.1.0 to before V3.1.5; update to V3.1.5 or later; Siemens CVSS v3.1 5.9, CWE-400. — Siemens ProductCERT
- Not in CISA KEV catalog version 2026.11.18 (1,786 entries); EPSS 0.38682, percentile 0.98607, dataset 2026-11-18. — CISA KEV / FIRST EPSS

Related advisories
Sources
- NVD
- OpenSSH 9.9p2 release notes (2025-02-18)
- OpenSSH security page
- Qualys Security Advisory: CVE-2025-26465 MitM and CVE-2025-26466 DoS
- oss-security: Qualys advisory post (2025-02-18)
- OpenSSH fix commit 6ce00f0
- Debian security tracker: CVE-2025-26466
- Red Hat: CVE-2025-26466
- Buildroot commit 002931cc: openssh security bump to 9.9p2
- OpenWrt packages commit f1bf549d: openssh bump to 9.9p2 (openwrt-24.10)
- OpenWrt packages: net/openssh Makefile (openwrt-23.05)
- Siemens ProductCERT SSA-398330
- CVE.org record CVE-2025-26466 (CNA: Red Hat)
- CISA KEV
- FIRST EPSS
Frequently asked questions
Which OpenSSH versions are affected by CVE-2025-26466?
sshd in OpenSSH 9.5p1 to 9.9p1 inclusive; the ping code that causes it was added in August 2023, shortly before 9.5p1. OpenSSH 9.9p2, released on 2025-02-18, fixes it. Vendor packages can differ from the upstream number: Red Hat lists RHEL 9, whose package is based on 8.7p1, as affected and fixed it in openssh-8.7p1-45.el9 (per the OpenSSH release notes, the Qualys advisory and Red Hat).
How can I limit CVE-2025-26466 without upgrading?
On OpenSSH 9.8p1 and later, PerSourcePenalties mitigates it; Qualys and Red Hat add that LoginGraceTime and MaxStartups are also needed for a full mitigation, because sshd allows 100 concurrent unauthenticated connections by default. Restricting the SSH port to a management network further reduces exposure (per the OpenSSH 9.9p2 release notes, the Qualys advisory and Red Hat).
Is the OpenSSH client also affected by CVE-2025-26466?
Qualys reports that the same unbounded PONG queue affects the client and that no client-side mitigation exists; it used the client-side memory consumption as part of its CVE-2025-26465 server impersonation attack. The OpenSSH release notes describe the server side, sshd(8) (per the Qualys advisory and the OpenSSH 9.9p2 release notes).
Which embedded builds and industrial products ship a fix for CVE-2025-26466?
Buildroot 2025.02, 2024.11.2 and 2024.02.11 ship OpenSSH 9.9p2, and the OpenWrt openwrt-24.10 packages branch moved to 9.9p2 on 2025-03-12; as of 2026-11-19 openwrt-23.05 and openwrt-22.03 carry 9.8p1. Siemens fixes it for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP GNU/Linux subsystem in V3.1.5 (per Buildroot, the OpenWrt packages repository and Siemens SSA-398330).
Is CVE-2025-26466 exploited in the wild?
It is not in the CISA KEV catalog as of 2026-11-19 (catalog version 2026.11.18). CISA's SSVC entry records a proof of concept, not active exploitation, and FIRST EPSS gives it 0.387, the 98.6th percentile, in the 2026-11-18 dataset (per CISA KEV, CVE.org and FIRST EPSS).
Questions about this page?