Skip to content
Threat Brief

← All advisories

CVE-2026-128088

Low 2.2No known exploitationFix available

russh try_sign: asynchronous confirmation can sign after agent lock

Vendor advisory: GHSA-736f-c93q-9fwx

Record last updated

CVSS score

2.2

Low on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.1%

Higher than 1% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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 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.

Weakness: CWE-367, CWE-863

Patching and mitigation

Patch status
Fix available (source: GitHub Advisory Database)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
Eugenyrussh>= 0.65.0, < 0.65.1Not documentedCVE Program
rustrussh0.65.00.65.1GitHub Advisory Database

Timeline

  1. Disclosure

    CVE record published by GitHub_M

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by GitHub Advisory Database

    Source: GitHub Advisory Database (opens in a new tab)

Vendor guidance and references