russh try_sign: asynchronous confirmation can sign after agent lock
Key facts
- Attack vector
- Local
- Privileges required
- Low
- User interaction
- Required
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Partial Red Hat: 1 without a fix
Attack profile from CVSS 3.1 · CNA. Fix status from CNA, GitHub and Red Hat. Impact type from CWE-863.
Summary
russh is a Rust SSH client and server library that includes an SSH agent protocol implementation. Prior to version 0.65.1, try_sign() captures an Arc<PrivateKey> before awaiting Agent::confirm() and does not revalidate the shared lock state or key presence after the await. This is a distinct residual defect in the remediation for CVE-2026-116794. A peer, including a remote SSH server using agent forwarding, can begin a confirmation-constrained signature request while the agent is unlocked and receive the signature after another connection locks the agent if the stale confirmation returns true. New post-lock requests are rejected and private key material is not disclosed, but the pending operation bypasses the current lock state. This issue is fixed in version 0.65.1.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Eugeny | russh | 0.65.0 to before 0.65.1 | 0.65.1 | Patch available | CNA |
| — | russh (crates.io) | 0.65.0 to before 0.65.1 | 0.65.1 | Patch available | GHSA-736f-c93q-9fwx |
- russh VendorEugeny Affected 0.65.0 to before 0.65.1 Fixed in 0.65.1 Patch available CNA
- russh (crates.io) Vendor— Affected 0.65.0 to before 0.65.1 Fixed in 0.65.1 Patch available GHSA-736f-c93q-9fwx
Remediation
- Fix · CNA russh (Eugeny) Fixed in 0.65.1
- Fix · GHSA-736f-c93q-9fwx russh (crates.io) Fixed in 0.65.1 Advisory →
Vendor assessments
Red Hat
Red Hat rating: Low. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Red Hat Hardened Images | Affected | No fix yet |
Timeline
- 2026-11-13 Threatist record created from CVE-2026-128088
- 2026-11-13 Alias added: GHSA-736f-c93q-9fwx
- 2026-11-13 Fix available: crates.io/[email protected] · GHSA-736f-c93q-9fwx
- 2026-11-13 CVSS score added · GHSA-736f-c93q-9fwx
- 2026-11-13 Weakness changed · GHSA-736f-c93q-9fwx
- 2026-11-13 5 new references · GHSA-736f-c93q-9fwx
- 2026-11-14 Affected versions changed · Red Hat
- 2026-11-14 CVSS score added · Red Hat
References
More Eugeny vulnerabilities
- TI-2026-65512 russh: Client-side channel-scoped Handler callbacks fire for channel IDs the client never opened CVSS 3.1HIGH 7.5
- TI-2026-35550 Russh: SSH message fields were decoded through allocation-first parsers before field-specific bounds CVSS 3.1HIGH 7.5
- TI-2026-34331 Russh: Post-decompression SSH packet size was not bounded, allowing remote oversized compressed packets CVSS 3.1HIGH 7.5
- TI-2026-34308 Resource allocation without limits in Eugeny russh CVSS 3.1HIGH 7.5
- TI-2025-16084 Tabby has a TCC Bypass via Misconfigured Node Fuses CVSS 4.0HIGH 8.6
- TI-2024-36991 Tabby has a TCC Bypass via Unnecessary Permissive Entitlements in Tabby CVSS 4.0HIGH 8.6
Sources
- CVE-2026-128088 · CVE Program
- CVE-2026-128088 · NVD
- FIRST EPSS
- GHSA-736f-c93q-9fwx · GitHub Advisory Database · CC BY 4.0
- CVE-2026-128088 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences