CVE-2026-48110

GHSA-4r3c-5hpg-58qr · RUSTSEC-2026-0494 · published 10 Jun 2026 · updated 12 Nov 2026

Russh: SSH message fields were decoded through allocation-first parsers before field-specific bounds

7.5HighCVSS 7.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in russh 0.61.0.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Eugeny>=0.34.0 <0.61.0
cargo: russh>=0.34.0 <0.61.00.61.0

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in russh (Cargo), strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-48110 severity on Zeptric[![CVE-2026-48110](https://zeptric.io/badge/cve/CVE-2026-48110.svg)](https://zeptric.io/cve/CVE-2026-48110)