Russh is a Rust SSH client & server library. From version 0.34.0-beta.1 to before version 0.61.0, russh did not enforce the SSH identification-string rules as deliberately as OpenSSH. In particular, the server-side identification reader used the same permissive path as the client, allowing pre-banner lines from clients, and the reader did not enforce a bounded number of pre-banner lines. For a library server built on russh, this could allow a remote peer to hold connection setup resources in the cleartext pre-authentication phase with malformed identification input that should have been rejected early. This issue has been patched in version 0.61.0.
CVE-2026-48108
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EPSS
- 19.5%
- KEV
- Not listed
Published
June 10, 2026
Last Modified
June 11, 2026
Advisory Details (1)
Auto-updated Jun 13, 2026SSH identification parsing accepted non-canonical client banners and did not bound pre-banner input · Advisory · Eugeny/russh · GitHub
https://github.com/Eugeny/russh/security/advisories/GHSA-76r6-x97p-67vrVendor Advisories for CVE-2026-48108(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
crates.io(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| russh | — | 0.61.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 63× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-07 03:26 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 11:08 UTCEG score recompute
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 11:39 UTCEG score recompute
- 2026-07-03 08:33 UTCEG score recompute
- 2026-07-02 10:11 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 11:56 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 13:41 UTCEG score recompute
- 2026-06-29 14:18 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 16:03 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 17:47 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 19:32 UTCEG score recompute
- 2026-06-25 21:17 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 23:02 UTCEG score recompute
Show 38 moreShow fewer
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-24 00:46 UTCEG score recompute
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 02:19 UTCEG score recompute
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 04:02 UTCEG score recompute
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 04:51 UTCEG score recompute
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-20 06:32 UTCEG score recompute
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-19 08:17 UTCEG score recompute
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 09:44 UTCEG score recompute
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 11:29 UTCEG score recompute
- 2026-06-16 17:53 UTCEPSS rescore
- 2026-06-16 13:14 UTCEG score recompute
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 14:24 UTCEG score recompute
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-14 16:05 UTCEG score recompute
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 17:49 UTCEG score recompute
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 19:30 UTCEG score recompute
- 2026-06-11 21:15 UTCEG score recompute
- 2026-06-11 14:00 UTCEPSS rescore
- 2026-06-10 23:01 UTCEG score recompute
- 2026-06-10 23:00 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-20
- CVE-2002-2444EG 9.8CRITICAL
- CVE-2005-0116NVD 0.0EG 9.0EPSS 99%NONE
- CVE-2002-1359NVD 0.0EG 9.0EPSS 100%NONE
- CVE-2000-0380NVD 0.0EG 9.0EPSS 98%NONE
- CVE-2000-0258EG 7.5EPSS 97%HIGH
- CVE-2004-2771EG 0.0EPSS 93%NONE
- CVE-2002-2443EG 0.0EPSS 93%NONE
- CVE-2002-2433EG 0.0NONE
- CVE-2003-1569EG 0.0NONE
- CVE-2003-1568EG 0.0NONE
Frequently asked(5)
What is CVE-2026-48108?
When was CVE-2026-48108 disclosed?
Is CVE-2026-48108 actively exploited?
What is the CVSS score of CVE-2026-48108?
How do I remediate CVE-2026-48108?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48108
Is Your Infrastructure Affected by CVE-2026-48108?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.