CVE 5.3 MEDIUM

russh server userauth state is not reset when authentication principal changes_CVE-2026-46705

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

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.

Basic Information

ID CVE-2026-46705
Source GitHub_M
Published Jun 10, 2026 at 20:21
Modified Jun 10, 2026 at 20:22

Affected Product

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

CWE Classification

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.