CVE-2026-116794
russh: Agent server never calls `Agent::confirm`, so keys added with the confirm constraint (`ssh-add -c`) sign without confirmation
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.
Fixes and workarounds
Fix
russh (crates.io): OSV reports a fixed version 0.65. Check the advisory for supported release branches.
Source: OSV GHSA-vp5q-ff62-jwqvAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| russh Eugeny |
< 0.65 (affected) | CNA: GitHub_M |
russhrussh
crates.io |
Ecosystem version events: introduced 0; fixed 0.65Source events (ECOSYSTEM)Other versions: unaffected |
OSV GHSA-vp5q-ff62-jwqv |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 8.3 high |
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 | CNA: GitHub_M |
Exploit evidence
- https://github.com/Eugeny/russh/security/advisories/GHSA-vp5q-ff62-jwqv
exploit · ADP: CISA-ADP
References
- https://github.com/Eugeny/russh/security/advisories/GHSA-vp5q-ff62-jwqvCNA: GitHub_M · x_refsource_CONFIRM
- https://github.com/Eugeny/russh/commit/3e04597dc54e36bfc85c21996f7d8d9d224e9826CNA: GitHub_M · x_refsource_MISC
- https://github.com/Eugeny/russh/commit/62db6e7defd6d244159da962ccccb029e785ce0fCNA: GitHub_M · x_refsource_MISC
- https://github.com/Eugeny/russh/releases/tag/v0.65.0CNA: GitHub_M · x_refsource_MISC
- https://github.com/Eugeny/russh/security/advisories/GHSA-vp5q-ff62-jwqvADP: CISA-ADP · exploit
- https://github.com/advisories/GHSA-vp5q-ff62-jwqvOSV / GitHub Security Advisories · advisory
- https://osv.dev/vulnerability/GHSA-vp5q-ff62-jwqvOSV / GitHub Security Advisories · osv
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/cveshttps://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.