Quick answers
- Is CVE-2026-116773 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116773 being exploited in the wild.
- How severe is CVE-2026-116773?
- Medium severity, with a CVSS score of 4.3, published 27 October 2026.
- Which products and versions are affected?
- russh (crates.io) < 0.65, ECOSYSTEM:introduced=0,fixed=0.65; Russh before 0.65.0.
- Is there a fix for CVE-2026-116773?
- Yes. russh (crates.io): upgrade to 0.65 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116773 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116773?
- Check whether you run russh (crates.io) or Russh at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- russh (crates.io): upgrade to 0.65 or later
cargo update -p russh
Technical details
A use-after-free in the client's Session::process_packet handler accepts unlimited private message number 7 (EXT_INFO) packets before authentication completes. The handle_ext_info function appends extension names to received_extensions without bounds checking or deduplication, allowing a malicious server to trigger progressive memory exhaustion. The fix applies rate-limiting to EXT_INFO message processing.
Affected products
- russh russh before 0.65.0
Identifiers
- CVE-2026-116773
- GHSA-4p9f-7p9m-5vfg
Timeline
- 2026-10-27: advisory
- 2026-10-25: patched