# CVE-2026-128088: russh try_sign: asynchronous confirmation can sign after agent lock


- **Severity:** Low 2.2 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-128088, GHSA-736f-c93q-9fwx, UBUNTU-CVE-2026-128088

## What is CVE-2026-128088?

CVE-2026-128088 is a low-severity vulnerability in Eugeny russh, published on 13 Nov 2026. 

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

Weakness: CWE-863 (Incorrect Authorization), CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2026-128088?

1 open source package ship an affected version, including russh.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `russh` | crates.io | `pkg:cargo/russh` | From 0.65.0 | 0.65.1 |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | fixed | `russh` | 0.65.1 |

## How do I fix CVE-2026-128088?

Upgrade russh to 0.65.1 or later.

## Is CVE-2026-128088 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-128088 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128088 and fix it if it is affected.

What it is: CVE-2026-128088 is a low-severity vulnerability in Eugeny russh, published on 13 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-128088 exists.

Affected packages and fixed versions:
- russh (crates.io): affected from 0.65.0; fixed in 0.65.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-128088/ (Markdown: https://insights.sbomify.com/CVE-2026-128088/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-128088
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-128088
- OSV: https://osv.dev/vulnerability/CVE-2026-128088

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-128088/
Summaries are generated and may contain mistakes; the official description above is the record.
