CVE-2026-46705
MEDIUMrussh server userauth state is not reset when authentication principal changes
Title source: cnaDescription
Russh is a Rust SSH client & server library. From version 0.34.0-beta.1 to before version 0.61.0, the russh server authentication path keeps internal userauth state across SSH_MSG_USERAUTH_REQUEST messages without separating that state when the request principal changes. RFC 4252 allows the user name and service name fields to change between authentication requests. The issue is not that such changes are invalid. The issue is that russh-owned authentication state, such as remaining methods, partial-success state, and in-progress method state, can remain associated with the connection and then influence a later request for a different (user, service). This is an internal library state mismatch. This issue has been patched in version 0.61.0.
References (1)
Core 1
Core References
X_Refsource_Confirm x_refsource_confirm
https://github.com/Eugeny/russh/security/advisories/GHSA-hpv4-5h6f-wqr3
Scores
CVSS v3
5.3
EPSS
0.0036
EPSS Percentile
27.8%
Attack Vector
NETWORK
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CISA SSVC
Vulnrichment
Exploitation
poc
Automatable
yes
Technical Impact
partial
Details
CWE
CWE-287
Status
published
Products (2)
crates.io/russh
0.34.0-beta.1 - 0.61.0crates.io
Eugeny/russh
>= 0.34.0-beta.1, < 0.61.0
Published
Jun 10, 2026
Tracked Since
Jun 11, 2026