Public vulnerability disclosure

CVE-2026-128088

russh try_sign: asynchronous confirmation can sign after agent lock

publishedCWE-367CWE-863

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.

Technical severity2.2 lowCVSS 3.1 · CNA: GitHub_M
Published2026-11-13Source updated 2026-11-13
Collected2026-11-132 attributed sources

Fixes and workarounds

Fix

russh (crates.io): OSV reports a fixed version 0.65.1. Check the advisory for supported release branches.

Source: OSV GHSA-736f-c93q-9fwx

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
russh
Eugeny
>= 0.65.0, < 0.65.1 (affected) CNA: GitHub_M
russh

russh
crates.io
0.65.0 (affected, crates.io)
≥ 0.65.0; < 0.65.1 (affected, semver); OSV events: introduced 0.65.0; fixed 0.65.1
Source events (semver)
[
  {
    "introduced": "0.65.0"
  },
  {
    "fixed": "0.65.1"
  }
]

Other versions: unaffected
OSV GHSA-736f-c93q-9fwx

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 2.2
low
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:NCNA: GitHub_M

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide