Skip to main content
VulnerabilityPublished

CVE-2026-116794: Eugeny russh · Missing Authorization

Affects Eugeny russhSource CVE Database V5

0

Not known to be exploited · CVSS 8.3 High : upgrade to 0.65 soon.

Data as of 28 Oct 2026, 17:42 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.65, 0.65.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade russh to 0.65; github/Eugeny/russh to 0.65.0.

Affected software

ProductAffectedFixed in
EugenyrusshAffected
  • <0.65
Fixed in
  • 0.65
crates.iogithub/Eugeny/russhpkg:cargo/github/Eugeny/russhOther threatsAffected
  • <0.65.0
Fixed in
  • 0.65.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade russh to version 0.65.0 or later, where this issue is fixed. No other mitigation is necessary as the fix addresses the missing authorization check directly.

Description

A missing authorization vulnerability exists in the russh Rust SSH client and server library versions prior to 0.65.0. The agent server incorrectly returns a hard-coded success for SSH_AGENT_CONSTRAIN_CONFIRM requests instead of performing the expected user approval or policy check. This allows processes with access to the agent socket, including remote forwarded agents, to use keys added with confirmation without actual user approval, potentially enabling unauthorized signing or authentication. The issue is fixed in version 0.65.0.

References

Community reviews

Loading reviews…