Skip to main content
VulnerabilityPublished

CVE-2026-48110: Eugeny russh · Improper Input Validation

Affects Eugeny russhSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 0.61.0 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.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.61.0
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.0.

Affected software

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

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.0 or later, where this improper input validation vulnerability is patched. No other mitigation or workaround is indicated. Patch status is not explicitly stated but the fix is included in version 0.61.0.

Description

Russh is a Rust SSH client & server library. From version 0.34.0 to before version 0.61.0, several russh client and server message handlers decoded attacker-controlled SSH strings, name-lists, and byte fields into owned allocations before applying field-specific bounds. A remote SSH peer could send oversized, high-fanout, or malformed length-prefixed fields and make the library allocate, attempt to allocate, or split data before rejecting input that should have been rejected earlier. This issue has been patched in version 0.61.0.

References

Community reviews

Loading reviews…