CVE-2026-116774

russh: peer-declared zero maximum packet size permanently stalls channel writes (silent AsyncWrite hang)

Published Oct 27, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
russh is a Rust SSH client and server library that includes an SSH agent protocol implementation. From 0.60.0 until 0.65.0, channel-open parsing accepts a peer-declared maximum_packet_size of zero and passes it into ChannelTx::poll_writable in russh/src/channels/io/tx.rs. The Channel::data, Channel::make_writer, and Channel::into_stream asynchronous write paths then calculate a writable size of zero and remain pending forever because window adjustments cannot satisfy a static zero packet maximum. An authenticated client can strand server writes, and a malicious server can strand client writes, allowing affected tasks, channels, and connections to accumulate without surfacing an error. This issue is fixed in version 0.65.0.

Analysis

AI-generated

Technical impact

The russh library accepts a peer‑declared maximum packet size of zero during channel‑open, which is then used to calculate the writable size in the asynchronous write path. Because window adjustments can never satisfy a zero packet maximum, every write operation blocks forever, causing tasks, channels, and connections to hang without reporting an error. This unbounded blocking is a form of uncontrolled resource consumption (CWE‑400) and an infinite loop (CWE‑835), enabling an authenticated client or a malicious server to stall writes and accumulate stalled connections, ultimately exhausting system resources and denying service.

Affected Systems

The vulnerable component is the russh library from Eugeny. Versions 0.60.0 through 0.65.0, inclusive, contain the flaw. The issue was resolved in release 0.65.0, which removes the zero packet size handling path.

Risk and Exploitability

The CVSS score of 4.3 classifies this as a low to moderate severity vulnerability. No EPSS score is available and the flaw is not listed in the CISA KEV catalog. An attacker must control either the SSH client or the server that uses the russh library in order to declare a zero maximum packet size. The silent hang makes detection difficult, but an accumulation of stalled connections can lead to resource exhaustion and a denial of service.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade russh to 0.65.0 or later; the fixed release removes the zero packet size path.
  • If an upgrade is not immediately possible, ensure that the SSH handshake rejects or limits zero maximum packet sizes by enforcing a minimum packet size in the peer configuration.
  • Implement monitoring for idle or stalled channel write operations and trigger session timeouts or cleanup to prevent resource buildup.

Generated by OpenCVE AI on October 27, 2026 at 21:49 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-fw5c-8223-6h42 russh: peer-declared zero maximum packet size permanently stalls channel writes (silent AsyncWrite hang)
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Eugeny
Eugeny russh
Vendors & Products Eugeny
Eugeny russh
Type Values Removed Values Added
Description russh is a Rust SSH client and server library that includes an SSH agent protocol implementation. From 0.60.0 until 0.65.0, channel-open parsing accepts a peer-declared maximum_packet_size of zero and passes it into ChannelTx::poll_writable in russh/src/channels/io/tx.rs. The Channel::data, Channel::make_writer, and Channel::into_stream asynchronous write paths then calculate a writable size of zero and remain pending forever because window adjustments cannot satisfy a static zero packet maximum. An authenticated client can strand server writes, and a malicious server can strand client writes, allowing affected tasks, channels, and connections to accumulate without surfacing an error. This issue is fixed in version 0.65.0.
Title russh: peer-declared zero maximum packet size permanently stalls channel writes (silent AsyncWrite hang)
Weaknesses CWE-400
CWE-835
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L'}

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-835

    Loop with Unreachable Exit Condition ('Infinite Loop')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 28, 2026, 4:13 PM
Reserved
Oct 26, 2026, 9:53 PM
Status
Deferred
Published
Oct 27, 2026, 9:18 PM
Modified
Oct 28, 2026, 5:18 PM
Severity
Moderate
Public date
Oct 27, 2026, 8:25 PM