PT-2026-118097

CVE-2026-111062

·

Published

2026-10-19

·

Updated

2026-11-06

Description by

CVSS 4.0
2.3
Low
MetricsAV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Name of the Vulnerable Software and Affected Versions russh versions 0.34.0-beta.1 through 0.63.3
Description The SSH server implementation fails to verify that the signature algorithm used in a public-key authentication signature matches the algorithm specified in the authentication request. In the server read auth request pk function within russh/src/server/encrypted.rs, the server uses the requested algorithm pubkey algo only to decode the key, while the actual signature verification relies on the algorithm embedded within the signature blob itself. This allows a client with a valid RSA private key to claim the use of rsa-sha2-512 while actually providing a valid ssh-rsa SHA-1 signature. This can lead to the bypass of security restrictions for servers that disable SHA-1 or result in misleading audit logs for applications that record the requested algorithm.
Recommendations Update to version 0.64.0. As a temporary mitigation, restrict the use of the server read auth request pk function or implement a manual check to ensure the signature algorithm matches the requested algorithm before completing authentication.
Exploitability
Exploit
Fix
Impacts
Researchers
Vendors
Affected products
Related identifiers
GHSA-J7H2-66J4-GHJF
Found an issue in the description? Have something to add? Feel free to write us 👾