Rust russh: Prior to version 0.65.1, try_sign() captures an Arc<PrivateKey> before awaiting Agent::confirm() and does
Affects rust-russhSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 2.2 Low · fixed in 0.65.1 : update rust-russh when convenient.
Data as of 18 Nov 2026, 16:07 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 2.2 |
|---|
- Patch
- Available – fixed in 0.65.1
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10rust-russhpkg:deb/ubuntu/rust-russh?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to rust-russh version 0.65.1 or later, where this issue is fixed. No additional mitigation is required as the fix addresses the residual defect in the agent lock state handling.
Description
A vulnerability in the Rust russh library prior to version 0.65.1 allows a stale confirmation to bypass the agent lock state during SSH agent forwarding. This occurs because try_sign() captures a private key reference before awaiting confirmation and does not revalidate the lock state afterward. Although new requests are blocked when the agent is locked, a pending signature request initiated while unlocked can complete after locking, potentially bypassing the lock state. The issue does not disclose private key material and is fixed in version 0.65.1.
References
- ubuntu.com/security/CVE-2026-128088 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-128088 (opens in a new tab)
- github.com/Eugeny/russh/security/advisories/GHSA-736f-c93q-9fwx (opens in a new tab)
- github.com/Eugeny/russh/pull/808 (opens in a new tab)
- github.com/Eugeny/russh/commit/43a46d67a80a7355fcd2fb25e7e00d79aec8184c (opens in a new tab)
- github.com/Eugeny/russh/releases/tag/v0.65.1 (opens in a new tab)