Unauthenticated memory exhaustion via allocation-first SSH parsing
Published Jun 10, 2026 · Updated Jun 10, 2026
Improper input validation in russh 0.34.0 through 0.60.2 allows remote attackers to exhaust process memory through crafted SSH messages. Affected handlers decode length-prefixed strings, bytes, and name-lists into owned allocations before borrowed parsing helpers enforce local field limits. Server-side KEXINIT parsing is reachable before authentication; high concurrency can raise memory use by gigabytes, and allocator failure can abort the process.
Summary
What happened
Improper input validation in russh 0.34.0 through 0.60.2 allows remote attackers to exhaust process memory through crafted SSH messages. Affected handlers decode length-prefixed strings, bytes, and name-lists into owned allocations before borrowed parsing helpers enforce local field limits. Server-side KEXINIT parsing is reachable before authentication; high concurrency can raise memory use by gigabytes, and allocator failure can abort the process.
The record
- CVE
- CVE-2026-48110
- Published
- Jun 10, 2026
- Updated
- Jun 10, 2026
- Vendor
- Russh Project
- Product
- russh
- Classifications
- CWE-20, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 10, 2026CVE publishedPublication date reported by the CVE source.
- Jun 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.34.0, < 0.61.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Concurrent pre-authentication KEXINIT parser harnessproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo