CVE-2026-116773 — Vulnerability intelligence
Eugeny — russh
Published:
- CVSS
- 4.3
- CISA KEV
- Not listed; not proof of no exploitation
Original source text (not a translation)
russh's SSH client is susceptible to unbounded allocations via EXT_INFO packets
### Summary
**All evidence, reproduction steps, and scripts in the report were verified against a real running instance. Nothing is fabricated or synthetic; every verdict is backed by captured output from an actual deployment.** Concretely, the evidence comes from executing the real russh v0.64.1 client packet parser (`Session::process_packet` handling `handle_ext_info`) in a live client session with attacker-supplied packet bodies in the pre-authentication state; the captured output below is from that real execution.
russh's client stores every extension name it parses out of an `EXT_INFO` packet into a per-session vector and never clears, caps, or deduplicates it (`russh/src/client/encrypted.rs:433`, field declared at `russh/src/session.rs:60`). The packet is accepted without limit in the pre-authentication states, so a server - which is exactly the attacker position for a client library, and remains one even after the client has verified its host key - can send an unbounded sequence of these packets and grow the client's memory for as long as the session lives: 400 packets of about 26 KB each, carrying 3000 extension names apiece, retained 49.1 MiB (about 4.8 times the wire bytes) with the vector reaching 1,200,000 entries, while an equal volume of banner packets retained nothing. Two details make this reachable in practice: russh accepts `EXT_INFO` in its pre-auth states with no budget of any kind (its automatic rekey read-limit only engages after authentication), and russh encodes `EXT_INFO` as its own private message number 7 rather than the 8308 value 82, so the check that might interoperate with a well-behaved peer is inoperative - the malicious server simply speaks number 7. The same growth pattern has been accepted by the project before for other pre-auth allocation sinks; this one is a cross-packet accumulator rather than a single-packet allocation, and none of the published advisories covers it.
### Details
The handler appends every parsed extension name to the session state with no bound:
```text
russh/src/client/encrypted.rs:433 (v0.64.1 = main = e5d80a07dc554480b6ea3b2e14adfc190407b627)
enc.received_extensions.push(name.clone()); // no cap, no dedup
russh/src/session.rs:60
pub received_extensions: Vec<String>, // lives for the whole session
```
The state machine routes `EXT_INFO` to this handler in both the `WaitingAuthServiceRequest` and `WaitingAuthRequest` states (`encrypted.rs:111`, `encrypted.rs:401`), i.e. before the user has authenticated, and the read-limit based automatic rekey that would otherwise throttle a flood is only allowed in the authenticated state, so no counter or budget applies pre-auth. The message number involved is russh's private constant `msg::EXT_INFO = 7` (`russh/src/msg.rs:32`, in place since 2022), while RFC 8308 assigns `EXT_INFO` the value 82: russh does advertise the ext-info capability in its key exchange initiation, so a standards-compliant peer would send the packet as message number 82 - which this parser does not process - but nothing prevents a hostile or compromised server from sending message number 7 directly, and the client parses it unconditionally. Each accepted entry costs several times its wire size once heap and string overhead are counted, and the vector is only ever read (an extension lookup by the awaiter layer), never trimmed. The affected code is identical on the latest tag v0.64.1 and on main (same commit e5d80a07dc554480b6ea3b2e14adfc190407b627), and the accumulation has existed since 2022, so all released client versions are affected.
### Proof of concept
The harness constructs a real client `Session` in the `WaitingAuthRequest` pre-auth state (the configuration a client holds while the server is asking for authentication), then feeds attacker-controlled packet bodies to the genuine `Session::process_packet` dispatch - the same function the network event loop calls - so the retention happens in the production parsing path, not a reimplementation. A counting global allocator measures live heap across packets. The control leg feeds the same packet volume of `USERAUTH_BANNER` bodies, which parse and dispatch without retention. The test below is added to the russh source tree as `russh/src/client/extinfo_poc.rs`, with two lines added to `russh/src/client/mod.rs` next to the existing test module declarations:
```rust
#[cfg(test)]
mod extinfo_poc;
```
```rust
cat > russh/src/client/extinfo_poc.rs <<'EOF'
//! PoC: unbounded pre-auth client memory growth
//! via repeated EXT_INFO packets (`received_extensions` accumulates without
//! cap or dedup; russh/src/client/encrypted.rs:handle_ext_info).
//!
//! Drives the REAL client packet parser (Session::process_packet ->
//! handle_ext_info) with attacker-supplied packet bodies over an unmodified
//! client session in the pre-auth state (WaitingAuthRequest). Measuring
//! allocator totals proves the growth is persistent and unbounded across
//! packets. Control leg: equal