CVE-2026-46705 russh server userauth state is not reset when authentication principal changes
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- Proof of concept public · automatable: yes · technical impact: partial
- Technology
- Debian
Description
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.
Upgrade path
3 packages: 2 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| crates.io russh(crates.io) | >= 0.34.0-beta.1, < 0.61.0 | 0.61.0 | Fixed |
| debian/rust-russh(Debian 14) | < 0.64.1-1; = 0.57.1-1; = 0.57.1-2 | 0.64.1-1 | Fixed |
| Eugeny russh | = >= 0.34.0-beta.1, < 0.61.0 | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| crates.io russh(crates.io) | >= 0.34.0-beta.1, < 0.61.0 | 0.61.0 |
| Eugeny russh | = >= 0.34.0-beta.1, < 0.61.0 | No fix listed |
| debian/rust-russh(Debian:14) | < 0.64.1-1 | 0.64.1-1 |
| debian/rust-russh(Debian:14) | = 0.57.1-1 | No fix listed |
| debian/rust-russh(Debian:14) | = 0.57.1-2 | No fix listed |
References
- https://github.com/Eugeny/russh/security/advisories/GHSA-hpv4-5h6f-wqr3 exploit vendor-advisory
- nvd.nist.gov third-party-advisory vendor-advisory
- github.com product
- github.com
- Debian Security Tracker CVE-2026-46705 vendor-advisory
- bugs.debian.org issue-tracking