Is CVE-2026-48110 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-48110 being exploited in the wild.

How severe is CVE-2026-48110?

High severity, with a CVSS score of 7.5, published 10 June 2026.

Which products and versions are affected?

russh (crates.io) SEMVER:introduced=0.34.0,fixed=0.61.0.

Is there a fix for CVE-2026-48110?

Yes. russh (crates.io): upgrade to 0.61.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-48110 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-48110?

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.

CVE-2026-48110: Russh resource exhaustion via improper input validation in SSH message handlers

CVE-2026-48110 · Severity: high · CVSS 7.5 · Published 2026-06-10

Russh is a library used to implement SSH (Secure Shell) connections in Rust applications. A vulnerability in how it handles incoming messages allows a remote attacker to force the application to consume excessive amounts of memory, potentially leading to a system crash or service outage. This can occur even before a user has logged in, making it a significant risk for publicly accessible SSH services.

Technologies: russh (crates.io). Vendors: crates.io.

Quick answers

Is CVE-2026-48110 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-48110 being exploited in the wild.
How severe is CVE-2026-48110?: High severity, with a CVSS score of 7.5, published 10 June 2026.
Which products and versions are affected?: russh (crates.io) SEMVER:introduced=0.34.0,fixed=0.61.0.
Is there a fix for CVE-2026-48110?: Yes. russh (crates.io): upgrade to 0.61.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-48110 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-48110?: 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.61.0 or later
```
cargo update -p russh
```

Technical details

The russh library's SSH message handlers for both clients and servers decoded attacker-controlled strings, name-lists, and byte fields into owned allocations (e.g., String, Vec, Bytes) before validating field-specific length bounds. An unauthenticated remote peer can send malformed or oversized length-prefixed fields, such as those in KEXINIT or USERAUTH_REQUEST messages, to trigger large memory allocations. In a high-concurrency scenario, this leads to significant RAM consumption or process termination due to allocator failure. The vulnerability is mitigated in version 0.61.0 by introducing borrowed, bounded parsing helpers that validate lengths before allocation.

Affected products

Eugeny russh >= 0.34.0, < 0.61.0

Identifiers

CVE-2026-48110
GHSA-4r3c-5hpg-58qr

Timeline

2026-05-20: advisory: Initial GitHub Advisory published
2026-06-11: patched: Version 0.61.0 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.