CVE-2026-46705 PUBLISHED

russh server userauth state is not reset when authentication principal changes

Assigner: GitHub_M
Reserved: 15.05.2026 Published: 10.06.2026 Updated: 11.06.2026

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.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CVSS Score: 5.3

Product Status

Vendor Eugeny
Product russh
Versions
  • Version >= 0.34.0-beta.1, < 0.61.0 is affected

References

Problem Types

  • CWE-287: Improper Authentication CWE