Missing confirmation check in russh SSH agent for constrained keys
Key facts
- Attack vector
- Local
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA, GitHub and Red Hat. Impact type from CWE-862.
Summary
The agent server in russh, a Rust SSH client and server library, returns success for keys added with the confirm constraint without calling the Agent::confirm hook, in versions from 0.50.0-beta.12 before 0.65.0. The missing authorization check (CWE-862) lets signing skip the user approval that an application's confirm policy requires. A local process that can reach the agent socket, or the remote side of a forwarded agent, can sign data as the user while the key stays loaded, if the application overrides Agent::confirm.
Written with Claude Haiku 5.5 from the sources below · 2026-11-03
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Eugeny | russh | before 0.65 | 0.65 | Patch available | CNA |
| — | russh (crates.io) | before 0.65 | 0.65 | Patch available | GHSA-vp5q-ff62-jwqv |
- russh VendorEugeny Affected before 0.65 Fixed in 0.65 Patch available CNA
- russh (crates.io) Vendor— Affected before 0.65 Fixed in 0.65 Patch available GHSA-vp5q-ff62-jwqv
Remediation
Upgrade russh to version 0.65.0. Red Hat Hardened Images is fixed in RHSA-2026:93904, released 2026-11-02.
Written with Claude Haiku 5.5 from the sources below · 2026-11-03
- Fix · CNA russh (Eugeny) Fixed in 0.65
- Fix · GHSA-vp5q-ff62-jwqv russh (crates.io) Fixed in 0.65 Advisory →
Red Hat 1 advisory
- RHSA-2026:93904 Released 2026-11-02 · Red Hat rating ModerateRed Hat Hardened Images RPMs Security Update
- Red Hat Hardened Images openshell-0.1.6-0.1.hum1@aarch64, openshell-0.1.6-0.1.hum1@src, openshell-0.1.6-0.1.hum1@x86_64 +4
Vendor assessments
Red Hat
Red Hat rating: Moderate. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Red Hat Hardened Images | Fixed | RHSA-2026:93904 |
Timeline
- 2026-10-28 Threatist record created from CVE-2026-116794
- 2026-10-30 Priority changed: MEDIUM → LOW
- 2026-10-30 Affected versions changed · Red Hat
- 2026-10-30 CVSS score added · Red Hat
- 2026-10-30 Alias added: GHSA-vp5q-ff62-jwqv
- 2026-10-30 Fix available: crates.io/[email protected] · GHSA-vp5q-ff62-jwqv
- 2026-10-30 CVSS score added · GHSA-vp5q-ff62-jwqv
- 2026-10-30 Weakness changed · GHSA-vp5q-ff62-jwqv
- 2026-10-30 6 new references · GHSA-vp5q-ff62-jwqv
- 2026-10-31 CVSS score changed · Red Hat
- 2026-11-03 Fix available: RHSA-2026:93904 · Red Hat
- 2026-11-03 Fix available: Red Hat Hardened Images · Red Hat
- 2026-11-03 CISA SSVC decision points changed
- 2026-11-03 Priority changed: LOW → HIGH
References
Other 5
- https://github.com/Eugeny/russh/security/advisories/GHSA-vp5q-ff62-jwqv
- https://github.com/Eugeny/russh/commit/3e04597dc54e36bfc85c21996f7d8d9d224e9826
- https://github.com/Eugeny/russh/commit/62db6e7defd6d244159da962ccccb029e785ce0f
- https://github.com/Eugeny/russh/releases/tag/v0.65.0
- https://github.com/Eugeny/russh
More Eugeny vulnerabilities
- TI-2026-65512 russh: Client-side channel-scoped Handler callbacks fire for channel IDs the client never opened CVSS 3.1HIGH 7.5
- TI-2026-35550 Russh: SSH message fields were decoded through allocation-first parsers before field-specific bounds CVSS 3.1HIGH 7.5
- TI-2026-34331 Russh: Post-decompression SSH packet size was not bounded, allowing remote oversized compressed packets CVSS 3.1HIGH 7.5
- TI-2026-34308 Resource allocation without limits in Eugeny russh CVSS 3.1HIGH 7.5
- TI-2025-16084 Tabby has a TCC Bypass via Misconfigured Node Fuses CVSS 4.0HIGH 8.6
- TI-2024-36991 Tabby has a TCC Bypass via Unnecessary Permissive Entitlements in Tabby CVSS 4.0HIGH 8.6
Sources
- CVE-2026-116794 · CVE Program
- CVE-2026-116794 · NVD
- FIRST EPSS
- GHSA-vp5q-ff62-jwqv · GitHub Advisory Database · CC BY 4.0
- CVE-2026-116794 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences