CVE-2026-116794
russh: Agent server never calls Agent::confirm, so keys added with the confirm constraint (ssh-add -c) sign without confirmation
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
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-116794 divulgada · CVSS 8.3 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Monitoreo | Fuente: ENISA EUVD | Registro visto por primera vez en ENISA EUVD | |
| Monitoreo | Fuente: OSV | Registro visto por primera vez en OSV | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación PoC pública | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
The russh Rust SSH library's agent server (in versions from 0.50.0-beta.12 through 0.65.0) fails to call the application's confirmation hook for keys added with the confirm constraint, so applications that rely on that hook to approve signing can have keys used without approval, including by a process or remote host reaching the agent socket. Applications that keep the default confirmation behavior or implement checks in the separate confirm_request hook are not affected by this flaw.
Affects russh agent servers where a key was added with the confirm constraint (ssh-add -c) and remains loaded. Fixed in russh 0.65.
Descripción original del registro (GitHub_M)
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.
Condiciones y alcance
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
russh |
Corregida | 0.65 | — | — |
0.65Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/Eugeny/russh/security/advisories/GHSA-vp5q-ff62-jwqvhttps://github.com/Eugeny/russh/commit/3e04597dc54e36bfc85c21996f7d8d9d224e9826https://github.com/Eugeny/russh/commit/62db6e7defd6d244159da962ccccb029e785ce0fhttps://github.com/Eugeny/russh/releases/tag/v0.65.0Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
