Quick answers
- Is CVE-2026-73489 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-73489 being exploited in the wild.
- How severe is CVE-2026-73489?
- Medium severity, with a CVSS score of 4.3, published 13 August 2026.
- Which products and versions are affected?
- russh (crates.io) SEMVER:introduced=0,fixed=0.62.4.
- Is there a fix for CVE-2026-73489?
- Yes. russh (crates.io): upgrade to 0.62.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-73489 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-73489?
- Check whether you run russh (crates.io) 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.62.4 or later
cargo update -p russh
Technical details
The vulnerability is a denial-of-service bug in the PTY request handler within russh/src/server/encrypted.rs. The parser uses a fixed 130-entry array for storing terminal modes but fails to validate the incoming mode count before processing; it continues incrementing the mode counter beyond array bounds and constructs an out-of-bounds slice, triggering a panic. The panic terminates the session task without memory corruption. Attack requires an already-authenticated SSH client with network access to the server. The issue is fixed in version 0.62.4 by adding proper bounds checking before processing terminal modes.
Affected products
- Eugeny Russh prior to 0.62.4
Identifiers
- CVE-2026-73489
- GHSA-cqjc-rmpq-xprq
Timeline
- 2026-08-13: disclosed
- 2026-07-22: patched: Fixed in version 0.62.4