[From nobody Mon Nov  9 16:37:07 2026
Received: (at submit) by bugs.debian.org; 31 Oct 2026 09:49:20 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-107.2 required=4.0 tests=ALL_TRUSTED,BAYES_00,
 DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,
 FROMDEVELOPER,SPF_HELO_NONE,SPF_PASS,USER_IN_DKIM_WELCOMELIST
 autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 43; hammy, 150; neutral, 154; spammy,
 0. spammytokens:
 hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
 0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
 0.000-+--H*RT:311, 0.000-+--H*RT:108
Return-path: &lt;carnil@debian.org&gt;
Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:43034)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from &lt;carnil@debian.org&gt;) id 1xN5iC-007N8i-2a
 for submit@bugs.debian.org; Sat, 31 Oct 2026 09:49:20 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; 
 s=smtpauto.stravinsky;
 h=X-Debian-User:Content-Type:MIME-Version:Message-ID:
 Subject:To:From:Date:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:
 Content-Description:In-Reply-To:References;
 bh=8GSduLqdoKhuUW6nQ/RI+1znNx0wMbBqvi44A2iNpX4=; b=X5xpb9m47CHgv81QYxJ13ZuB5I
 uB4v0LQK/38gRz98cdzUSR9Zhy3iLQc2/yvAeRIh846sdKjAStsWhM4utBXAK5QFWoFykXZeXJAT7
 P2d1JMlf+lDp0r/SwOJfqcIYwPb8x5jjYqWolC0NnfJTriwYqCCyJtdrjoY3Q+2Kn0Bofytb8T+qQ
 nG9cdIs89wIAPqM36mqML3Bd8b/1E92LWcZlPhEN79jco+qkLvYkTg5zD7jce+l8nMtl069F7IHlu
 qWDj1TVr+z+MnBbCkSfaaD5h6IfH+F4VQ3ixNzxolP7KX5Xc5ky0z58syozHS8RaE5bisRUkfgftr
 pYJkSj3w==;
Received: from authenticated-user by stravinsky.debian.org with esmtpsa
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from &lt;carnil@debian.org&gt;) id 1xN5iA-004VnA-0D
 for submit@bugs.debian.org; Sat, 31 Oct 2026 09:49:19 +0000
Received: by eldamar.lan (Postfix, from userid 1000)
 id AE8E8DC0386; Sat, 31 Oct 2026 10:49:17 +0100 (CET)
Date: Sat, 31 Oct 2026 10:49:17 +0100
From: Salvatore Bonaccorso &lt;carnil@debian.org&gt;
To: submit@bugs.debian.org
Subject: rust-russh: CVE-2026-116696 CVE-2026-116773 CVE-2026-116774
 CVE-2026-116794
Message-ID: &lt;auW5nUwMiE7P4C9c@eldamar.lan&gt;
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Debian-User: carnil
Delivered-To: submit@bugs.debian.org

Source: rust-russh
Version: 0.64.1-2
X-Debbugs-CC: team@security.debian.org
Severity: grave
Tags: security upstream

Hi,

The following vulnerabilities were published for rust-russh.

CVE-2026-116696[0]:
| russh is a Rust SSH client and server library that includes an SSH
| agent protocol implementation. Prior to 0.65.0,
| russh::keys::agent::server::serve in russh/src/keys/agent/server.rs
| accepts repeated SSH_AGENT_CONSTRAIN_CONFIRM records while adding a
| key and appends every Constraint::Confirm record to the key's
| retained constraint vector without a count or memory limit. A
| process that can connect to the agent socket, including the remote
| side of a forwarded agent session, can repeatedly add constrained
| keys and cause renewable memory growth that persists for the process
| lifetime because keys without a lifetime constraint do not expire.
| This issue is fixed in version 0.65.0.


CVE-2026-116773[1]:
| russh is a Rust SSH client and server library that includes an SSH
| agent protocol implementation. Prior to 0.65.0, the client
| Session::process_packet path in russh/src/client/encrypted.rs
| accepts repeated packets encoded with russh's private msg::EXT_INFO
| = 7 before authentication, while the standards-compliant EXT_INFO
| message number 82 does not reach the affected handler. The
| handle_ext_info function appends every parsed extension name to
| received_extensions without clearing, deduplicating, or bounding the
| vector. A malicious SSH server that deliberately sends private
| message number 7 can therefore retain an unbounded number of
| attacker-controlled extension names for the session lifetime,
| causing progressive client memory exhaustion. This issue is fixed in
| version 0.65.0.


CVE-2026-116774[2]:
| 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.


CVE-2026-116794[3]:
| russh is a Rust SSH client and server library that includes an SSH
| agent protocol implementation. From 0.50.0-beta.12 until 0.65.0, the
| agent server's Connection::try_sign path in
| russh/src/keys/agent/server.rs recognizes
| SSH_AGENT_CONSTRAIN_CONFIRM but returns a hard-coded successful
| result instead of calling Agent::confirm. In applications that
| override Agent::confirm to require user approval or another policy
| check, a process that can reach the agent socket, including the
| remote side of a forwarded agent, can use a key added through ssh-
| add -c without that check and can authenticate or sign data as the
| user while the key remains loaded. The separate
| Agent::confirm_request hook still runs for every signing request, so
| checks implemented there remain effective, and implementations that
| retain the default always-successful Agent::confirm do not lose an
| approval check through this regression. This issue is fixed in
| version 0.65.0.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities &amp; Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-116696
    https://www.cve.org/CVERecord?id=CVE-2026-116696
[1] https://security-tracker.debian.org/tracker/CVE-2026-116773
    https://www.cve.org/CVERecord?id=CVE-2026-116773
[2] https://security-tracker.debian.org/tracker/CVE-2026-116774
    https://www.cve.org/CVERecord?id=CVE-2026-116774
[3] https://security-tracker.debian.org/tracker/CVE-2026-116794
    https://www.cve.org/CVERecord?id=CVE-2026-116794

Regards,
Salvatore
]