CVE-2026-128087 json
russh kex_done: shared-secret callback runs before server host-key verification
published 11d ago modified yesterday also EUVD-2026-125719 , GHSA-9264-jvgf-6w2f
- cvss
- 3.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
russh is a Rust SSH client and server library that includes an SSH agent protocol implementation. From version 0.55.0 until version 0.65.1, the initial key exchange invokes client::Handler::kex_done() with the raw shared secret before check_server_key() accepts the server host key or certificate. A malicious SSH server can therefore trigger application-defined secondary-channel initialization or early data handling even when the server identity is subsequently rejected. Ordinary clients that keep the callback's no-op default or independently defer callback-derived actions until trust is confirmed are not affected. This issue is fixed in version 0.65.1.
Patch / fix
- crates.io russh 0.65.1
- github.com/Eugeny/russh@43a46d6 commit
- github.com/Eugeny/russh#808 pull request
- github.com/Eugeny/russh/releases/tag/v0.65.1 release
Is CVE-2026-128087 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-128087 updated cvss 3.7
russh: russh: Information disclosure via premature callback execution prior to host verification
-
Red Hat Hardened Images openshell 0.1.8-0.1.hum1affected: workaround, no fix available
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-14).
Exploits and checks
- github.com https://github.com/Eugeny/russh/security/advisories/GHSA-9264-jvgf-6w2f referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | russh | >=0.55.0, <0.65.1 |
0.65.1 |
Affected products
- Eugeny russh
Classification
References
Sources
- CVE List CVE-2026-128087
- GitHub Advisory GHSA-9264-jvgf-6w2f
- NVD CVE-2026-128087
- Maintainer advisory GHSA-9264-jvgf-6w2f
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of Eugeny/russh published their own advisory on GitHub. Reviewed sources take precedence over it.