cve.bz

CVE-2026-128087 russh kex_done: shared-secret callback runs before server host-key verification

3.7 lowFix available

Low (3.7) in eugeny russh. Fixed in russh 0.65.1.

On this page
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.

Severity

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-696 Incorrect Behavior Order
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-128087 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-128087?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-128087?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-128087 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-128087

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-128087](https://cve.bz/cve/badge/CVE-2026-128087.svg)](https://cve.bz/cve/CVE-2026-128087)

HTML:

<a href="https://cve.bz/cve/CVE-2026-128087"><img src="https://cve.bz/cve/badge/CVE-2026-128087.svg" alt="CVE-2026-128087"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Eugeny russh>= 0.55.0, < 0.65.1

Fix and patched versions

  • russh (crates.io): fixed in 0.65.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-9264-jvgf-6w2fcrates.iorussh>=0.55.0 <0.65.10.65.1

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON