Skip to main content
VulnerabilityPublished

CVE-2026-46702: Eugeny russh · Unthrottled Resource Allocation

Affects Eugeny russhSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 0.61.1 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.61.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade russh and github/eugeny/russh to 0.61.1.

Affected software

ProductAffectedFixed in
EugenyrusshAffected
  • >=0.34.0 <0.61.1
Fixed in
  • 0.61.1
crates.iogithub/eugeny/russhpkg:cargo/github/eugeny/russhOther threatsAffected
  • >=0.34.0 <0.61.1
Fixed in
  • 0.61.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade russh to version 0.61.1 or later, where this vulnerability has been patched. Patch status is confirmed by the version information in the advisory. No other mitigation is indicated.

Description

Russh is a Rust SSH client & server library. From version 0.34.0 to before version 0.61.1, when SSH compression is enabled, russh accepted compressed packets whose on-wire size passed the normal transport packet-length checks but whose decompressed size was much larger. This allowed a remote peer to send oversized post-decompression packets that should have been rejected. In current releases, this is a remote denial-of-service / resource-exhaustion issue in the post-decompression receive path. In older releases before 0.58.0, the same remote decompression path used CryptoVec, which appears to make the historical impact worse. This issue has been patched in version 0.61.1.

References

Community reviews

Loading reviews…