CVE-2026-46705

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 88% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Russh is a Rust SSH client & server library. From version 0.34.0-beta.1 to before version 0.61.0, the russh server authentication path keeps internal userauth state across SSH_MSG_USERAUTH_REQUEST messages without separating that state when the request principal changes. RFC 4252 allows the user name and service name fields to change between authentication requests. The issue is not that such changes are invalid. The issue is that russh-owned authentication state, such as remaining methods, partial-success state, and in-progress method state, can remain associated with the connection and then influence a later request for a different (user, service). This is an internal library state mismatch. This issue has been patched in version 0.61.0.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
12.2%
KEV
Not listed

Published

May 29, 2026

Last Modified

June 11, 2026

Advisory Details (1)

Auto-updated Jun 17, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

russh server userauth state is not reset when authentication principal changes · Advisory · Eugeny/russh · GitHub

https://github.com/Eugeny/russh/security/advisories/GHSA-hpv4-5h6f-wqr3

Vendor Advisories for CVE-2026-46705(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)
PackageVulnerable rangeFixed inDependents
russh—0.61.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 51× 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.

  1. 2026-07-16 01:50 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-14 13:55 UTCEG score recompute
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-12 05:46 UTCEPSS rescore
  8. 2026-07-11 17:23 UTCEG score recompute
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-08 17:17 UTCEG score recompute
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-07 13:46 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-02 03:50 UTCEG score recompute
  19. 2026-07-01 15:07 UTCEPSS rescore
  20. 2026-07-01 01:28 UTCEG score recompute
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-29 21:09 UTCEG score recompute
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-28 19:30 UTCEG score recompute
Show 47 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-27 17:51 UTCEG score recompute
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-26 16:12 UTCEG score recompute
  7. 2026-06-25 13:49 UTCEPSS rescore
  8. 2026-06-25 06:19 UTCEG score recompute
  9. 2026-06-24 14:05 UTCEPSS rescore
  10. 2026-06-24 02:52 UTCEG score recompute
  11. 2026-06-23 21:33 UTCEPSS rescore
  12. 2026-06-23 21:33 UTCEPSS rescore
  13. 2026-06-22 14:25 UTCEPSS rescore
  14. 2026-06-22 14:25 UTCEPSS rescore
  15. 2026-06-21 14:56 UTCEPSS rescore
  16. 2026-06-21 14:56 UTCEPSS rescore
  17. 2026-06-21 01:59 UTCEPSS rescore
  18. 2026-06-21 01:59 UTCEPSS rescore
  19. 2026-06-19 19:26 UTCEPSS rescore
  20. 2026-06-19 19:26 UTCEPSS rescore
  21. 2026-06-18 17:52 UTCEPSS rescore
  22. 2026-06-18 17:52 UTCEPSS rescore
  23. 2026-06-18 03:16 UTCEG score recompute
  24. 2026-06-17 17:53 UTCEPSS rescore
  25. 2026-06-17 01:29 UTCEG score recompute
  26. 2026-06-16 17:53 UTCEPSS rescore
  27. 2026-06-15 23:50 UTCEG score recompute
  28. 2026-06-15 17:49 UTCEPSS rescore
  29. 2026-06-14 22:11 UTCEG score recompute
  30. 2026-06-13 23:00 UTCEPSS rescore
  31. 2026-06-13 20:31 UTCEG score recompute
  32. 2026-06-12 23:12 UTCEPSS rescore
  33. 2026-06-12 23:12 UTCEPSS rescore
  34. 2026-06-12 18:49 UTCEG score recompute
  35. 2026-06-11 17:10 UTCEG score recompute
  36. 2026-06-11 14:00 UTCEPSS rescore
  37. 2026-06-10 15:32 UTCEG score recompute
  38. 2026-06-09 13:53 UTCEG score recompute
  39. 2026-06-08 12:15 UTCEG score recompute
  40. 2026-06-07 10:36 UTCEG score recompute
  41. 2026-06-06 08:58 UTCEG score recompute
  42. 2026-06-05 07:19 UTCEG score recompute
  43. 2026-06-04 05:40 UTCEG score recompute
  44. 2026-06-03 04:01 UTCEG score recompute
  45. 2026-06-02 02:21 UTCEG score recompute
  46. 2026-06-01 00:42 UTCEG score recompute
  47. 2026-05-29 20:20 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46705?
CVE-2026-46705 is a medium vulnerability published on May 29, 2026. Russh is a Rust SSH client & server library. From version 0.34.0-beta.1 to before version 0.61.0, the russh server authentication path keeps internal userauth state across SSHMSGUSERAUTH_REQUEST messages without separating that state when the request principal changes. RFC 4252 allows the user name…
When was CVE-2026-46705 disclosed?
CVE-2026-46705 was first published in the National Vulnerability Database on May 29, 2026, with the most recent update on June 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46705 actively exploited?
CVE-2026-46705 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46705?
CVE-2026-46705 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-46705?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46705, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46705

Explore →

Is Your Infrastructure Affected by CVE-2026-46705?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs