CVE-2026-116773: russh's SSH client is susceptible to unbounded allocations via EXT_INFO packets

Published Oct 27, 2026
·
Updated

russh is a Rust SSH client and server library that includes an SSH agent protocol implementation. Prior to 0.65.0, the client Session::processpacket path in russh/src/client/encrypted.rs accepts repeated packets encoded with russh's private msg::EXTINFO = 7 before authentication, while the standards-compliant EXTINFO message number 82 does not reach the affected handler. The handleextinfo function appends every parsed extension name to receivedextensions without clearing, deduplicating, or bounding the vector. A malicious SSH server that deliberately sends private message number 7 can therefore retain an unbounded number of attacker-controlled extension names for the session lifetime, causing progressive client memory exhaustion. This issue is fixed in version 0.65.0.

Affected Software

1 affected component
cargo/russh<0.65.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade russh to a version that resolves this vulnerability.

    Fixed in 0.65.0

Event History

Oct 27, 2026
CVE Published
via MITRE·08:23 PM
Data Sourced
via MITRE·08:23 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Applications using russh as an SSH client and processing connections to untrusted or malicious SSH servers are exposed if they use a version before 0.65.0. The affected path is in the client Session::process_packet handling before authentication.

2

What must an attacker do to trigger the memory exhaustion?

An attacker must operate or control an SSH server that the client connects to and send repeated packets using russh's private EXT_INFO message number 7 before authentication. The standards-compliant EXT_INFO message number 82 does not reach the affected handler.

3

Does exploitation require authentication or user interaction?

No authentication is required because the affected packet handling occurs before authentication. A client must connect to the malicious SSH server, after which the server can progressively consume client memory by sending repeated crafted packets.

4

What is the remediation?

Upgrade russh to version 0.65.0, which fixes the unbounded accumulation of parsed extension names.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203