Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-736f-c93q-9fwx | russh try_sign: asynchronous confirmation can sign after agent lock |
Fri, 13 Nov 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Eugeny
Eugeny russh |
|
| Vendors & Products |
Eugeny
Eugeny russh |
Fri, 13 Nov 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | russh try_sign: asynchronous confirmation can sign after agent lock | |
| Weaknesses | CWE-367 CWE-863 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-11-13T19:07:42.568Z
Reserved: 2026-11-12T21:24:51.131Z
Link: CVE-2026-128088
No data.
Status : Deferred
Published: 2026-11-13T19:19:31.630
Modified: 2026-11-13T19:19:31.743
Link: CVE-2026-128088
No data.
OpenCVE Enrichment
Updated: 2026-11-13T21:30:21Z
Github GHSA