# CVE-2026-116794: russh is a Rust SSH client and server library that includes an SSH agent protocol implementation.


- **Severity:** High 8.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-116794, GHSA-vp5q-ff62-jwqv

## What is CVE-2026-116794?

CVE-2026-116794 is a high-severity vulnerability in Eugeny russh, published on 28 Oct 2026. 

### Official description

russh is a Rust SSH client and server library that includes an SSH agent protocol implementation. From 0.50.0-beta.12 until 0.65.0, the agent server's Connection::try_sign path in russh/src/keys/agent/server.rs recognizes SSH_AGENT_CONSTRAIN_CONFIRM but returns a hard-coded successful result instead of calling Agent::confirm. In applications that override Agent::confirm to require user approval or another policy check, a process that can reach the agent socket, including the remote side of a forwarded agent, can use a key added through ssh-add -c without that check and can authenticate or sign data as the user while the key remains loaded. The separate Agent::confirm_request hook still runs for every signing request, so checks implemented there remain effective, and implementations that retain the default always-successful Agent::confirm do not lose an approval check through this regression. This issue is fixed in version 0.65.0.

Weakness: CWE-862 (Missing Authorization)

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


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

No fix has been published for CVE-2026-116794 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116794 being exploited?

There is no known exploitation of CVE-2026-116794 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116794 is a high-severity vulnerability in Eugeny russh, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116794 in the wild and no public exploit code.

Affected product: Eugeny russh. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-116794/ (Markdown: https://insights.sbomify.com/CVE-2026-116794/index.md)
```

## Sources

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

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