Skip to main content
VulnerabilityPublished

CVE-2026-116696: Eugeny russh · Unthrottled Resource Allocation

Affects Eugeny russhSource CVE Database V5

0

Not known to be exploited · CVSS 3.3 Low : upgrade to 0.65.0 when convenient.

Data as of 27 Oct 2026, 20:42 UTC

CVSS 3.1 base score
3.3Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.65.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 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 and github/Eugeny/russh to 0.65.0.

Affected software

ProductAffectedFixed in
EugenyrusshAffected
  • <0.65.0
Fixed in
  • 0.65.0
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 indicated or necessary as the fix addresses the root cause by limiting resource allocation.

Description

CVE-2026-116696 is a resource allocation vulnerability in the russh Rust SSH client and server library prior to version 0.65.0. The issue occurs in the SSH agent protocol implementation where repeated SSH_AGENT_CONSTRAIN_CONFIRM records can be added without limits, causing unbounded memory growth. This memory growth persists for the lifetime of the process because keys without lifetime constraints do not expire. The vulnerability is fixed in russh version 0.65.0.

References

Community reviews

Loading reviews…