Debian Package Tracker
Register | Log in
Subscribe

rust-russh

Client and server SSH library - Rust source code

Choose email to subscribe with

general
  • source: rust-russh (main)
  • version: 0.65.1-2
  • maintainer: Debian Rust Maintainers (archive) (DMD)
  • uploaders: kpcyrd (DMD)
  • arch: any
  • std-ver: 4.7.4
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • testing: 0.64.1-2
  • unstable: 0.65.1-2
versioned links
  • 0.64.1-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 0.65.1-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • librust-russh-dev
action needed
Marked for autoremoval on 14 December: #1152685 high
Version 0.64.1-2 of rust-russh is marked for autoremoval from testing on Mon 14 Dec 2026. It is affected by #1152685. The removal of rust-russh will also cause the removal of (transitive) reverse dependencies: dromedary, rust-dromedary, rust-hussh, rust-sftp. You should try to prevent the removal by fixing these RC bugs.
Created: 2026-11-07 Last update: 2026-11-18 07:02
A new upstream version is available: 0.65.2 high
A new upstream version 0.65.2 is available, you should consider packaging it.
Created: 2026-11-17 Last update: 2026-11-18 04:47
6 security issues in forky high

There are 6 open security issues in forky.

6 important issues:
  • CVE-2026-116696: 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: 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: 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: 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.
  • CVE-2026-128087: russh is a Rust SSH client and server library that includes an SSH agent protocol implementation. From version 0.55.0 until version 0.65.1, the initial key exchange invokes client::Handler::kex_done() with the raw shared secret before check_server_key() accepts the server host key or certificate. A malicious SSH server can therefore trigger application-defined secondary-channel initialization or early data handling even when the server identity is subsequently rejected. Ordinary clients that keep the callback's no-op default or independently defer callback-derived actions until trust is confirmed are not affected. This issue is fixed in version 0.65.1.
  • CVE-2026-128088: russh is a Rust SSH client and server library that includes an SSH agent protocol implementation. Prior to version 0.65.1, try_sign() captures an Arc<PrivateKey> before awaiting Agent::confirm() and does not revalidate the shared lock state or key presence after the await. This is a distinct residual defect in the remediation for CVE-2026-116794. A peer, including a remote SSH server using agent forwarding, can begin a confirmation-constrained signature request while the agent is unlocked and receive the signature after another connection locks the agent if the stale confirmation returns true. New post-lock requests are rejected and private key material is not disclosed, but the pending operation bypasses the current lock state. This issue is fixed in version 0.65.1.
Created: 2026-10-28 Last update: 2026-11-14 17:01
The package has not entered testing even though the delay is over normal
The package has not entered testing even though the 2-day delay is over. Check why.
Created: 2026-11-12 Last update: 2026-11-18 07:01
21 open merge requests in Salsa normal
There are 21 open merge requests for this package on Salsa. You should consider reviewing and/or merging these merge requests.
Created: 2026-11-01 Last update: 2026-11-16 23:00
lintian reports 2 warnings normal
Lintian reports 2 warnings about this package. You should make the package lintian clean getting rid of them.
Created: 2026-06-02 Last update: 2026-10-07 10:31
debian/patches: 3 patches to forward upstream low

Among the 3 debian patches available in version 0.65.1-2 of the package, we noticed the following issues:

  • 3 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.
Created: 2026-05-06 Last update: 2026-11-10 11:32
testing migrations
  • excuses:
    • Migrates after: rust-hussh
    • Migration status for rust-russh (0.64.1-2 to 0.65.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
    • Issues preventing migration:
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/amd64 to testing makes Build-Depends of src:dromedary uninstallable
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/amd64 to testing makes librust-dromedary-dev/0.1.11-1/amd64 uninstallable
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/amd64 to testing makes librust-sftp-dev/0.3.0-2/amd64 uninstallable
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/arm64 to testing makes librust-dromedary-dev/0.1.11-1/arm64 uninstallable
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/arm64 to testing makes librust-sftp-dev/0.3.0-2/arm64 uninstallable
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/armhf to testing makes librust-dromedary-dev/0.1.11-1/armhf uninstallable
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/armhf to testing makes librust-sftp-dev/0.3.0-2/armhf uninstallable
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/i386 to testing makes librust-dromedary-dev/0.1.11-1/i386 uninstallable
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/i386 to testing makes librust-sftp-dev/0.3.0-2/i386 uninstallable
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/loong64 to testing makes librust-dromedary-dev/0.1.11-1/loong64 uninstallable
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/loong64 to testing makes librust-sftp-dev/0.3.0-2/loong64 uninstallable
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/ppc64el to testing makes librust-dromedary-dev/0.1.11-1/ppc64el uninstallable
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/ppc64el to testing makes librust-sftp-dev/0.3.0-2/ppc64el uninstallable
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/riscv64 to testing makes librust-dromedary-dev/0.1.11-1/riscv64 uninstallable
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/riscv64 to testing makes librust-sftp-dev/0.3.0-2/riscv64 uninstallable
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/s390x to testing makes librust-dromedary-dev/0.1.11-1/s390x uninstallable
    • ∙ ∙ migrating librust-russh-dev/0.65.1-2/s390x to testing makes librust-sftp-dev/0.3.0-2/s390x uninstallable
    • ∙ ∙ Implicit dependency: rust-russh rust-hussh
    • Additional info (not blocking):
    • ∙ ∙ Updating rust-russh will fix bugs in testing: #1152685
    • ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-russh.html
    • ∙ ∙ Autopkgtest for rust-russh/0.65.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • ∙ ∙ Reproduced on amd64 - info
    • ∙ ∙ Reproduced on arm64 - info
    • ∙ ∙ Reproduced on armhf - info
    • ∙ ∙ Reproduced on i386 - info
    • ∙ ∙ Required age reduced by 3 days because of autopkgtest
    • ∙ ∙ 8 days old (needed 2 days)
    • Not considered
news
[rss feed]
  • [2026-11-09] Accepted rust-russh 0.65.1-2 (source) into unstable (kpcyrd)
  • [2026-11-09] Accepted rust-russh 0.65.1-1 (source) into experimental (kpcyrd)
  • [2026-10-15] rust-russh 0.64.1-2 MIGRATED to testing (Debian testing watch)
  • [2026-10-11] Accepted rust-russh 0.64.1-2 (source) into unstable (kpcyrd)
  • [2026-10-06] Accepted rust-russh 0.64.1-1 (source) into unstable (kpcyrd)
  • [2026-07-27] rust-russh REMOVED from testing (Debian testing watch)
  • [2026-06-07] rust-russh 0.57.1-2 MIGRATED to testing (Debian testing watch)
  • [2026-06-01] Accepted rust-russh 0.57.1-2 (source) into unstable (Peter Michael Green)
  • [2026-05-19] rust-russh 0.57.1-1 MIGRATED to testing (Debian testing watch)
  • [2026-05-06] Accepted rust-russh 0.57.1-1 (amd64 source) into unstable (Debian FTP Masters) (signed by: kpcyrd)
bugs [bug history graph]
  • all: 0
links
  • homepage
  • lintian (0, 2)
  • buildd: logs, reproducibility, cross
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 0.57.1-2

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing