https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 31 Oct 2026 11:46:26 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-116794 <p>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&#39;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.</p> <p>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&#39;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.</p> https://db.gcve.eu/vuln/fkie_cve-2026-116794 https://db.gcve.eu/vuln/ghsa-vp5q-ff62-jwqv <p><strong>Affected:</strong> crates.io: russh</p> <p>### Summary</p> <p>The agent server in `russh::keys::agent::server` never calls `Agent::confirm` before signing with a key that was added with the confirm constraint. That constraint is `SSH_AGENT_CONSTRAIN_CONFIRM` (RFC 9987 §5.2.7.2), which is what `ssh-add -c` sends.</p> <p>The call was replaced by a hard-coded `true` in 3e04597 (&#34;Native async traits encore&#34;, #455), first released in 0.50.0-beta.12. Every release since, up to and including 0.64.1, signs requests for confirm-constrained keys without asking the `Agent` implementation. A user who added a key with `-c` is therefore never asked to confirm.</p> <p>### Details</p> <p>`Connection::try_sign` notes that the key needs confirmation, then awaits a ready future instead of the agent ([server.rs L348-L360 at v0.64.1](https://github.com/Eugeny/russh/blob/e5d80a07dc554480b6ea3b2e14adfc190407b627/russh/src/keys/agent/server.rs#L348-L360)):</p> <p>```rust let agent = if needs_confirm { let (agent, ok) = { let _pk = key.clone(); Box::new(futures::future::ready((agent, true))) } .await; if !ok { return Ok((agent, false)); } agent } else { agent }; ```</p> <p>Before [3e04597](https://github.com/Eugeny/russh/commit/3e04597dc54e36bfc85c21996f7d8d9d224e9826) the first statement was `let (agent, ok) = agent.confirm(key.clone()).await;`.</p> <p>`try_sign` was checked in the published crates on crates.io: - Every russh release from 0.50.0-beta.12 to 0.64.1 (52 versions) has the hard-coded `true`. - russh 0.50.0-beta.8 to be…</p> <p><strong>Affected:</strong> crates.io: russh</p> <p>### Summary</p> <p>The agent server in `russh::keys::agent::server` never calls `Agent::confirm` before signing with a key that was added with the confirm constraint. That constraint is `SSH_AGENT_CONSTRAIN_CONFIRM` (RFC 9987 §5.2.7.2), which is what `ssh-add -c` sends.</p> <p>The call was replaced by a hard-coded `true` in 3e04597 (&#34;Native async traits encore&#34;, #455), first released in 0.50.0-beta.12. Every release since, up to and including 0.64.1, signs requests for confirm-constrained keys without asking the `Agent` implementation. A user who added a key with `-c` is therefore never asked to confirm.</p> <p>### Details</p> <p>`Connection::try_sign` notes that the key needs confirmation, then awaits a ready future instead of the agent ([server.rs L348-L360 at v0.64.1](https://github.com/Eugeny/russh/blob/e5d80a07dc554480b6ea3b2e14adfc190407b627/russh/src/keys/agent/server.rs#L348-L360)):</p> <p>```rust let agent = if needs_confirm { let (agent, ok) = { let _pk = key.clone(); Box::new(futures::future::ready((agent, true))) } .await; if !ok { return Ok((agent, false)); } agent } else { agent }; ```</p> <p>Before [3e04597](https://github.com/Eugeny/russh/commit/3e04597dc54e36bfc85c21996f7d8d9d224e9826) the first statement was `let (agent, ok) = agent.confirm(key.clone()).await;`.</p> <p>`try_sign` was checked in the published crates on crates.io: - Every russh release from 0.50.0-beta.12 to 0.64.1 (52 versions) has the hard-coded `true`. - russh 0.50.0-beta.8 to be…</p> https://db.gcve.eu/vuln/ghsa-vp5q-ff62-jwqv