Advisory

RUSTSEC-2026-0492

Also known as: CVE-2026-102823, GHSA-47hw-gvq5-r2gm

Summary

Client Handler callbacks run for channels the client never opened

Details

On the client side, russh passed channel messages from the server (data, extended data, EOF, close, success, failure, open failure and the exit-status, exit-signal and xon-xoff requests) to the application's client::Handler callbacks without checking that the channel number belonged to a channel the client had opened and the server had confirmed. The server side already performed this check.

A malicious or compromised SSH server can therefore send these messages for any channel number, including the next number the client will allocate (they are assigned in order) or one it has already closed. An application that tracks per-channel state can be made to record a false exit status, see a channel close before its real output arrives, or panic when it looks up a channel it does not know.

From 0.63.1 the client ignores channel messages for channels that are not established and confirmed, and handles an open failure only for a channel it is actually opening.

Severity

High Basis: CVSS v3 score 7.5, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Dates

Published
2026-09-30 12:00 UTC
Modified
2026-11-12 08:00 UTC

Affected packages and fixes

russh

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.63.1 (semver)

Fixed versions

0.63.1

Fix

  • Fixed version 0.63.1
    cargo update -p russh --precise 0.63.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences